On Wed, 20 Feb 2019 at 16:44, Steve Dower
On 20Feb2019 0839, Paul Moore wrote:
On Wed, 20 Feb 2019 at 16:28, Steve Dower
wrote: 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.
Sorry for the drive-by comment (I don't have time to read the PEP right now) but does this mean that "pip install --upgrade" won't be supported against __pypackages__ directories (it currently doesn't work properly with --target, IIRC - certainly *some* things go weird with --target) or will the PEP include mechanisms to allow pip to work more cleanly with __pypackages__ than it currently does with --target?
The PEP explicitly doesn't say anything about what pip can/should do (at Donald's request), but the assumption is that it will support it properly. (Hence "*emulate* *most* of the PEP".)
My point is just that the intent is for it to be a "normal" package directory, not a reimagining of packaging.
OK, cool. Thanks for clarifying. I suspect there's some non-trivial work needed for pip to support __pypackages__ (and potentially some questions at the interop standards level about how "installation frontends" should work in general when faced with __pypackages__), but that's fine. I just wanted to call out that it might not be trivial or transparent. Paul