Re: Implement Python Externally Managed Environments (PEP 668)

[Greg Troxel <gdt%lexort.com@localhost>]

Kimmo Suominen <kim%netbsd.org@localhost> writes:

> Wed, 12 Jun 2024 19:52:26 +0300 (15 weeks, 5 days, 7 hours ago)

> I'd like to see Python in pkgsrc implement the Externally Managed
> Environments spec to have pip and other Python installers guide users
> towards virtual environments by default, instead of installing in the
> paths that are expected to be managed by pkgsrc.
>
> https://packaging.python.org/en/latest/specifications/externally-managed-environments/
>
> Any suggestions on the best way to implement that?

I saved your message, but didn't say anything because I felt I didn't
really understand the brave nee py-world, and hoped somebody else would.

But since they didn't...

It looks like the above link says that distribution-managed python
installs should have an EXTERNALLY-MANAGED file, and that's all that is
needed.

That will mean that pip will object, and I hope it's overridable,
because I think people should be able to install a package in pkgsrc,
and then install from sources a slightly tweaked or newer version, for
debugging/validation/etc.  (Yes I know one can make dist and then
package that, and I've done that too.)

Do you see any approach other than having python3.X packages put that
file there?  And then somehow, tell packages built under pkgsrc that
it's ok to use that path?

Have you tried it?