feat: add py-pip to env
Let's put py-pip
into the ESD as use cases often rely on pip install …
and we can't rely on the system-installed version of pip.
(I.e. it's plain luck that those use cases worked before.)
(FYI @kindler)
Merge request reports
Activity
@emuller yes, I think that would make more sense:
spack.yaml
only includes EBRAINS top-level packages, everything needed for specific use-cases should go into awf-
package (and packages only needed for the Lab installation should go intosite-config/ebrainslab/spack.yaml
)On the other hand, since we include all dependencies in the
wf-
packages, needingpip
at all seems a bit weird?ebrains-drive
specifically, that is mentioned in @kindler's email, is already part of the ESD.I agree, something like
ebrains-drive
should be included in the ESD, but I believe there are still many use cases where people just install something… I can't judge if those cases are valid or just bad style.I.e. let's cover all the use cases in
wf-*
, but allow for people to do dirty stuff? (wish/goal vs. reality)I believe, @kindler will check if the ESD-provided
py-ebrains-drive
(andpy-hbp-neuromorphic-platform
) work (and imho those should work → if they don't we better fix that first) → i.e. this adding a "pip" use case doesn't look time-critical to me.Edited by Eric Mülleradded 1 commit
- b03956c1 - feat: add wf/usecase for user-customized python envs
added 12 commits
-
b03956c1...232e774f - 11 commits from branch
master
- f4fe6f52 - feat: add wf/usecase for user-customized python envs
-
b03956c1...232e774f - 11 commits from branch
added 1 commit
- 5ddd5fef - feat: add wf/usecase for user-customized python envs
added 12 commits
-
5ddd5fef...232e774f - 11 commits from branch
master
- 129cbeff - feat: add wf/usecase for user-customized python envs
-
5ddd5fef...232e774f - 11 commits from branch
py-pip
has been added to the ESD, and it's now possible to runpip install ...
in the experimental kernel in the Lab. However, keep in mind that (as decided in the past) if someone tries to install a package that is already installed as part of the ESD, the ESD version will be used, unlesssys.path
is fixed manually.