Post #2563351
2024-08-27 09:12 UTC
@stargirl@hachyderm.io Rephrasing @corbin@defcon.social, I'd say that "Python Packaging" is actually solved. Mostly. Everything-pyproject.toml (maybe with PEP-725) is comprehensive for what's truly in scope for "python packaging". There will necessarily be some native stuff that is absolutely out of scope for "python packaging", in fact most of it. There will always have to be a "system layer" under "python packages".
Nixpkgs is one consumer that integrates PEP-compliant "python packages" with its "native" stuff
Replies (1)
-
@nobody@mastodon.acm.org 2024-08-27 09:17
@stargirl@hachyderm.io @corbin@defcon.social Nobody asked for this opinion, but I think what needs solving instead is python imports. Specifically, first class multi-tenancy support which would remove the urge for writing things like https://discuss.python.org/t/allowing-multiple-versions-of-same-python-package-in-pythonpath/2219