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 brett.cannon, christian.heimes, ncoghlan, steve.dower, vstinner
Date 2017-12-16.16:33:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513442021.27.0.213398074469.issue32324@psf.upfronthosting.co.za>
In-reply-to
Content
The more interesting part is the relative directory and how often is it resolved? Can you change a program's imports by inducing it to change its working directory immediately after startup (or before any lazy imports)? If so, we should resolve it to a full path when adding it, regardless of -I.

Having the first entry there is required for local imports to work from the startup script, so I don't see it going anywhere. There have been many discussions about how to deal with the shadowing "problem", but the eventual answer was consenting adults.
History
Date User Action Args
2017-12-16 16:33:41steve.dowersetrecipients: + steve.dower, brett.cannon, ncoghlan, vstinner, christian.heimes
2017-12-16 16:33:41steve.dowersetmessageid: <1513442021.27.0.213398074469.issue32324@psf.upfronthosting.co.za>
2017-12-16 16:33:41steve.dowerlinkissue32324 messages
2017-12-16 16:33:41steve.dowercreate