PEP 668: "Graceful cooperation between external and Python package managers" #2056
Conversation
|
I think we can just pick an arbitrary PEP number, probably under the PEP 5XX range. |
|
You can take PEP 668. |
|
Looks like the build script does not like @dstufft and @pradyunsg switching to new email addresses. |
geofft
force-pushed
the
pip-only-in-virtualenv
branch
from
5b1b31a to
013d50d
Compare
geofft
changed the title
|
Numbered as PEP 668, switched to the email addresses @dstufft and @pradyunsg are already using in this repo, and set Discussions-To pointing to the Discourse thread. |
geofft
force-pushed
the
pip-only-in-virtualenv
branch
from
013d50d to
fb07e15
Compare
geofft
force-pushed
the
pip-only-in-virtualenv
branch
from
fb07e15 to
381903e
Compare
geofft
force-pushed
the
pip-only-in-virtualenv
branch
from
381903e to
e605832
Compare
| ``conda`` command generally only operates on Conda-created | ||
| environments, most of the concerns in this document do not apply | ||
| to ``conda`` when acting as a Python-specific package manager.) | ||
| distro package manager |
There was a problem hiding this comment.
FWIW Conda supports installing Python packages via the pip CLI in its environment.yml files: https://github.com/conda/conda/blob/master/tests/conda_env/support/advanced-pip/environment.yml
So making sure we know where packages came from will come in handy in the future.
Plus, there is a off-by-default feature to take Python packages into consideration in the dependency solver stage: https://docs.conda.io/projects/conda/en/latest/user-guide/configuration/pip-interoperability.html It's likely that this will be enabled by default in the future to improve interoperability since it's something Conda users have requested heavily.
This PEP came out of discussions at the "Python in Distros" sprint at PyCon in May. It's been discussed a bit on linux-sig.
cc @doko42 @FFY00 @dstufft @uranusjr @stefanor @ehashman @pradyunsg.