You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered a few issues when setting up things (Ubuntu 18.10 with conda 4.7.12 and python 3.7.4 ). Since they all relate I am raising them in this one issue.
After conda create --name pyrk there were several issues with package versions when running pip install -r env.pip after running conda activate pyrk. It turns out that in pyrk python 2.7 was being used from /usr/bin/python rather than python 3.7 from anaconda. It would probably be better to change the env creation command to conda create --name pyrk python=3.7 (or suitable python 3.X) to avoid this problem.
Since the assumption is that we are already in a conda env perhaps it's best to rm conda==4.5.12 from env.pip? Otherwise there is a version error anyway.
The coffea install in env.pip -e git+https://github.com/CoffeaTeam/coffea.git@da7d16002148a77e5dc05d8fe994e15c5a92b21c#egg=coffea fails due to a ModuleNotFoundError, not finding six. This is caused by six not actually being installed yet. It is only really installed when the pip command is successfully completed, which it isn't due to the coffea install error. I had to comment out the coffea line, run pip install -r env.pip once, then uncomment and run again.
I had to rm the explicit subdirectory in the coffea install line
Speaking of coffea, it looks like coffea is already included as a submodule. Perhaps better to just install it using pip like everything else?
The text was updated successfully, but these errors were encountered:
Sorry for the long silence, I stopped developing pyrk for a while, I might resume now, but we are not sure which option will be the final one. Some answers:
Sure, makes sense, even though I think you might have installed the conda2 which defaults to python2, using miniconda3 it defaults to python 3, but I agree that more safety is better
yeah, agreed
I will try shuffling the pip packages
I do not understand what you changed, can you be more specific?
I'd rather stay with the submodule, there is a good chance that we might have to hack into coffea to add some utilities we need, having it as a submodule makes everything easier
I encountered a few issues when setting up things (Ubuntu 18.10 with conda 4.7.12 and python 3.7.4 ). Since they all relate I am raising them in this one issue.
After
conda create --name pyrk
there were several issues with package versions when runningpip install -r env.pip
after runningconda activate pyrk
. It turns out that inpyrk
python 2.7 was being used from/usr/bin/python
rather than python 3.7 from anaconda. It would probably be better to change the env creation command toconda create --name pyrk python=3.7
(or suitable python 3.X) to avoid this problem.Since the assumption is that we are already in a conda env perhaps it's best to rm
conda==4.5.12
from env.pip? Otherwise there is a version error anyway.The coffea install in env.pip
-e git+https://github.com/CoffeaTeam/coffea.git@da7d16002148a77e5dc05d8fe994e15c5a92b21c#egg=coffea
fails due to aModuleNotFoundError
, not findingsix
. This is caused bysix
not actually being installed yet. It is only really installed when the pip command is successfully completed, which it isn't due to the coffea install error. I had to comment out the coffea line, runpip install -r env.pip
once, then uncomment and run again.I had to rm the explicit subdirectory in the coffea install line
Speaking of coffea, it looks like coffea is already included as a submodule. Perhaps better to just install it using pip like everything else?
The text was updated successfully, but these errors were encountered: