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 Anthony Sottile, Antony.Lee, Chris Billington, Ivan.Pozdeev, __Vano, barry, brett.cannon, christian.heimes, eric.smith, eric.snow, ethan smith, jaraco, mhammond, ncoghlan, pitrou, takluyver, terry.reedy, vstinner
Date 2019-01-13.20:02:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> To make a potentially viable concrete proposal here, I think a reasonable first step would be to change the ".pth" file processing code in to emit PendingDeprecationWarning for the 'if line.startswith(("import ", "import\t")):' branch.

PendingDeprecationWarning because you don’t think we can remove this functionality in 3.9?

> In addition to helping to determine the scope of the compatibility break being discussed here, such a warning would also be usable as a debugging tool.
> I'd also suggest updating "python -m site" to list any pth files that it finds, and categorise them as simple sys.path additions (which are generally fine), and arbitrary code (which can be problematic).

Great idea, +1
Date User Action Args
2019-01-13 20:02:28barrysetrecipients: + barry, mhammond, brett.cannon, terry.reedy, jaraco, ncoghlan, pitrou, vstinner, eric.smith, christian.heimes, __Vano, eric.snow, takluyver, Antony.Lee, Ivan.Pozdeev, Anthony Sottile, ethan smith, Chris Billington
2019-01-13 20:02:26barrylinkissue33944 messages
2019-01-13 20:02:25barrycreate