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 minrk
Recipients brett.cannon, christian.heimes, eric.snow, lemburg, minrk, ncoghlan, r.david.murray, tdsmith, vstinner
Date 2015-06-30.18:52:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks for the feedback, I thought it might be a long shot. I will go back to removing the *use* of the feature everywhere I can find it, since it is so problematic and rarely, if ever, desirable.

> it's an essential feature that has been documented for a very long time

The entirety of the documentation of this feature appears to be this sentence on that page:

> Lines starting with import (followed by space or tab) are executed.

No explanation or examples are given, nor any reasoning about the feature or why one might use it.

> This change will basically break all Python applications

This surprises me. Can you elaborate? I have not seen an application rely on executing code in .pth files.

> If you believe that we can smoothly move to a world without .pth files, 
> you should propose an overall plan, step by step.

I have no desire to remove .pth files. .pth files are a fine way to add locations to sys.path. It's .pth files *executing arbitrary code* that's the problem, very surprising, and a source of many errors (especially how it is used in setuptools).
Date User Action Args
2015-06-30 18:52:18minrksetrecipients: + minrk, lemburg, brett.cannon, ncoghlan, vstinner, christian.heimes, r.david.murray, eric.snow, tdsmith
2015-06-30 18:52:18minrksetmessageid: <>
2015-06-30 18:52:18minrklinkissue24534 messages
2015-06-30 18:52:18minrkcreate