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 ncoghlan
Recipients Ivan.Pozdeev, barry, brett.cannon, christian.heimes, eric.smith, eric.snow, ethan smith, mhammond, ncoghlan, pitrou, takluyver
Date 2018-07-04.09:59:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1530698399.32.0.56676864532.issue33944@psf.upfronthosting.co.za>
In-reply-to
Content
To avoid confusing the discussions, two PEPs is likely a better option:

1. Designing and implementing a dedicated preload mechanism
2. Adjusting the way pth file handling works, including deprecating and removing the "pth arbitrary file execution" trick (depends on the first one as the forward compatible migration path for legitimate code preloading use cases)
History
Date User Action Args
2018-07-04 09:59:59ncoghlansetrecipients: + ncoghlan, mhammond, barry, brett.cannon, pitrou, eric.smith, christian.heimes, eric.snow, takluyver, Ivan.Pozdeev, ethan smith
2018-07-04 09:59:59ncoghlansetmessageid: <1530698399.32.0.56676864532.issue33944@psf.upfronthosting.co.za>
2018-07-04 09:59:59ncoghlanlinkissue33944 messages
2018-07-04 09:59:59ncoghlancreate