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 terry.reedy
Recipients Ivan.Pozdeev, barry, brett.cannon, christian.heimes, eric.smith, eric.snow, ethan smith, mhammond, ncoghlan, pitrou, takluyver, terry.reedy
Date 2018-07-05.18:09:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This issue, as stated, looks like a severe regression to me.

In each of my python installs, Lib/site-packages has a file called 'python.pth' containing 'F:/Python'.  This is not a glob of inscrutable code.  It is not even Python code.  Just a path.  Is this issue about something else also called a 'pth file'?

F:/Python latter is a package development directory on my supplementary hard drive.  When I first install a new version of Python (early alpha), I copy this tiny file.  Voila!  The packages within /Python are 'installed' for the new version without making copies.  Editing a file edits it for all 'installs'.  Deleting the directory for an old and no longer needed version does not delete any of my files.

Import in files within F:/Python/pack act as if pack were installed in the site package for the version of python running the file.  I can easily run anything in Command Prompt with 'py -x.y -m pack.file'.  I can easily rerun with a different version by hitting up arrow and changing x.y.  Command Prompt's current working directory does not matter.

I think this is one of Python's most under-appreciated features.  I am rather sure there is no way to so easily get the same effect.  Abuse of a great feature is not a good reason to delete it completely.
Date User Action Args
2018-07-05 18:09:27terry.reedysetrecipients: + terry.reedy, mhammond, barry, brett.cannon, ncoghlan, pitrou, eric.smith, christian.heimes, eric.snow, takluyver, Ivan.Pozdeev, ethan smith
2018-07-05 18:09:27terry.reedysetmessageid: <>
2018-07-05 18:09:27terry.reedylinkissue33944 messages
2018-07-05 18:09:27terry.reedycreate