PEP 668: "Graceful cooperation between external and Python package managers"

[geofft]

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.

[FFY00]

I think we can just pick an arbitrary PEP number, probably under the PEP 5XX range.

[JelleZijlstra]

You can take PEP 668.

[uranusjr]

Looks like the build script does not like @dstufft and @pradyunsg switching to new email addresses.

[geofft]

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.

[jezdez]

Hi all, I work on Conda in my day job and have met with @geofft to talk about Conda's relation with this, just thought I add a few notes here for posterity.

[jezdez]

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.