Conversation
VarenyaJ
requested review from
SmartMonkey-git
and removed request for
SmartMonkey-git
| conda activate p5 | ||
| pip install -r requirements.txt \ | ||
| -r requirements_scripts.txt \ | ||
| -r requirements_test.txt |
There was a problem hiding this comment.
This is wrong, no? There is a file for this.
There was a problem hiding this comment.
This only creates the env without the environment.yml. I could have used it but when the proxy error occured I wanted to test if I could first make the environment, and then populate it with packages afterwards (pip is not blocked by Charité)
There was a problem hiding this comment.
And why would you want to create the env without the environment.yml?
There was a problem hiding this comment.
Just to test if only the environment needs to be created - I recognized that it was a problem with conda being blocked and wanted to isolate the problem of creating the environment without worrying about all the packages we needed to install
| export SSL_CERT_FILE=$(python -c "import certifi; print(certifi.where())") | ||
|
|
||
| # now retry | ||
| conda env create -f requirements/environment.yml -n p5 |
There was a problem hiding this comment.
are you sure -n p5 is needed?
There was a problem hiding this comment.
Not necessarily if we're using the environment.yml, this was just carried over when I was writing the amended README after engaging in the later steps
SmartMonkey-git
left a comment
SmartMonkey-git
left a comment
There was a problem hiding this comment.
I would not add this to our code base. Its not really a part of the project and bloats our readme.
I dont think we should account for every situation the project might end up in.
You can document this rather on teams.
Would you be fine with me adding it to an Issue? I want to keep this documented somewhere, in case someone or one of us runs into this problem again and does not know why it's happening. I feel that it's also good to note since the last group discussion revealed people are weary about conda, and this is just to show that conda is not the problem but some workaround is needed if the network is blocking Anaconda repositories |
Yes, keep it in teams. Then others of our group can also use it. |
I meant that I realize this is bloating the README, so I want to move it to |
|
Will revisit later |
2 participants
Add warnings about Conda connection problems due to organization proxies blocking anaconda