Skip to content

setup errors (and suggested improvements) #2

@tpmccauley

Description

@tpmccauley

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.

  1. 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.

  2. 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.

  3. 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.

  4. I had to rm the explicit subdirectory in the coffea install line

  5. Speaking of coffea, it looks like coffea is already included as a submodule. Perhaps better to just install it using pip like everything else?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions