I noticed this issue:

conda env export | tee environment.yml
# why are packages from ~/.local/lib/python2.7/site-packages included?


which python
python -m path
PYTHONNOUSERSITE=1 python -m path

Should conda install pip; pip install --user install packages outside of CONDA_ENV or CONDA_ROOT?
- I think the answer is no (because as a user, I assume conda environments to be self-contained and thereby reproducible)
Where should conda install pip; pip install --user install packages?
- CONDA_ROOT?
  - (edit) either:
    - conda install -n root readme and conda install pip; pip install --user readme would both install to CONDA_ROOT/lib/pythonX.X/site-packages
    - ... pip install --user readme would install to CONDA_ROOT/.local/pythonX.X/site-packages
Should conda python, by default, read packages from ~/.local/lib/python2.7?
- I think the answer here is also no (for the same reason).

python agnostic

If reproducibility is the ultimate objective, IDK how this is relevant?
IIUC, we are to assume that conda python is wholly independent of what else is installed on the system?

Workarounds:

always manually set PYTHONUSERSITE=1
- impractical when directly calling things in ${CONDA_ENV}/bin
virtualenvwrapper: echo 'export PYTHONUSERSITE=1' >> "${VIRTUAL_ENV}/bin/postactivate"

Possible solutions:

Patch the cpython user-site directory to a subpath of CONDA_ROOT:
- https://www.python.org/dev/peps/pep-0370/
- https://github.com/ContinuumIO/anaconda-recipes/blob/master/python-2.7/site.patch
  - sitecustomize.py?

Missing --no-site-packages option #394

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions