This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barry
Recipients barry, brett.cannon, christian.heimes, eric.smith, eric.snow, ethan smith, ncoghlan, pitrou, takluyver
Date 2018-06-25.01:28:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On Jun 23, 2018, at 18:56, Nick Coghlan <> wrote:
> My request (wearing my "BDFL-delegate for packaging interoperability standards" hat) is that proponents of the change resist the temptation to view the problem that way :)
> Path files are used extensively across the Python packaging ecosystem to implement additional environment management features beyond those provided natively by interpreter implementations, and while we've added native equivalents for some of them (namespace packages, virtual environments), we're far from having added support for all of them (dynamic package version selection, virtual environment chaining, editable package installs that still publish correct PEP 376 package metadata, etc).

Still, I firmly believe they’re a wart being abused for purposes they weren’t really intended for.  It’s a trick of implementation that lines beginning with `import` are exec’d.  That being said…

> Or, alternatively, the idea can be broken up into smaller, lower impact changes that still help to address the import system and end user environment maintainability issues, but don't involve breaking backwards compatibility.

+1 on working on *much* better debuggability and discoverability for .pth files first, and then consider their eventual deprecation, replacement, and/or removal.
Date User Action Args
2018-06-25 01:28:57barrysetrecipients: + barry, brett.cannon, ncoghlan, pitrou, eric.smith, christian.heimes, eric.snow, takluyver, ethan smith
2018-06-25 01:28:57barrylinkissue33944 messages
2018-06-25 01:28:55barrycreate