On 20Feb2019 0803, Dan Ryan wrote:
One final thing this enables as far as I understand is a sort of npm-like option for ignoring resolution conflicts and simply performing a sort of nested installation of subdependencies inside a top level dependency’s __pypackages__ folder. So if you did install two packages with a conflict, they wouldn’t necessarily have to find a resolution.
I'm not sure where you got this idea from? It's certainly not part of the proposal.
To be totally clear, and maybe this needs to be in the PEP (probably in three more various forms to make sure everyone gets it), you can emulate most of the PEP today with "pip install --target __pypackages__/3.7 ..." and "$env:PYTHONPATH = './__pypackages__/3.7'". Nothing else changes. The advantage is that even this amount of friction goes away.
My only concerns with this PEP relate to bloat. I’d be interested in ways to reduce duplication across a system with many such folders.
Are you interested in ways to reduce duplication across a system with many virtual environments? Again, there's literally no difference here (except under the PEP there isn't a need to _also_ duplicate the Python binaries).
(And I snipped your concern about scripts/bin folders, but that's very much an point of open discussion. It really relies on some integration with whatever terminal a user happens to be using, and so far, the PEP does not concern itself with modifying PATH, only sys.path.)
Cheers, Steve -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-le...@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/B4G7OZIWHTUOW7B2Z2DFI5YNXQPFMIQD/
