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 steve.dower
Recipients RusselWebber, Traveler Hauptman, docs@python, eric.snow, paul.moore, steve.dower, tim.golden, zach.ware
Date 2022-01-27.23:46:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643327169.18.0.268494792966.issue31582@roundup.psfhosted.org>
In-reply-to
Content
I think we need somewhere in the documentation to explain how the initial import path is calculated, in terms useful for an end user (rather than what's in getpath.py, which is for developers).

Right now, I'm not sure there's a good place for it. There's a Windows-specific page with some detail, but we probably need something more generic. Probably it belongs under Doc/using/cmdline.rst (the environment variables section there is tempting, but I expect those would be updated to point to an easier to follow explanation. We'd also point to it from sys.path.

Without adding the new section, there isn't really anywhere sensible to mention it.
History
Date User Action Args
2022-01-27 23:46:09steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, docs@python, eric.snow, zach.ware, Traveler Hauptman, RusselWebber
2022-01-27 23:46:09steve.dowersetmessageid: <1643327169.18.0.268494792966.issue31582@roundup.psfhosted.org>
2022-01-27 23:46:09steve.dowerlinkissue31582 messages
2022-01-27 23:46:09steve.dowercreate