-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doing an environment file #27
Comments
Hello @DavidjWhite33 <https://github.com/DavidjWhite33> and Yorguin,
Are both of you work on VNM?
If yes, maybe it's time we will roll out the standard conda environment for
VNM, and make sure it's BIDScoin and MNE-python ready?
If not, is there anything preventing you from working through VNM?
Best,
Oren
…On Tue, Jul 27, 2021 at 9:57 AM Yorguin José Mantilla Ramos < ***@***.***> wrote:
relevant
https://stackoverflow.com/questions/48787250/set-up-virtualenv-using-a-requirements-txt-generated-by-conda
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB7FUIZAZXRU5CRI247ZFDLTZXY4XANCNFSM5ARNWYLQ>
.
|
I would not make this dependent on VNM - it should be a standard conda or pip environment that can be reproduced in any python setup. There is no standard conda environment in VNM and will not exist any time soon. |
@civier I have not done any sovabids testing using VNM. If a sovabids conda env is set up, I am happy to give a go on VNM (and elsewhere). |
At the start of the development I did it with the VNM, nevertheless I was more comfortable with the development with my windows desktop. I figured the package should work in the VNM since the test of the CI worked.
I agree with this The main reason I have not done the environment file yet is because I dont want set the environment manually, requiring me to update it everytime I change something. I mainly want to have some process that saves the last environment sovabids was known to work so that if some package breaks some functionality, the user can install that environment that had the working versions of the packages. |
@DavidjWhite33 commented that:
I agree with this. I think one of the issues with python packages is that they can break because of the dependencies' updates. In that sense I think having an environment or requirements file that also says the last version of the dependencies the package worked with would be useful.
The text was updated successfully, but these errors were encountered: