homepage

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 BreamoreBoy, ThurnerRupert, eric.smith, laurent.birtz, ncoghlan, r.david.murray, terry.reedy, tim.golden
Date 2013年11月13日.13:56:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384351008.08.0.372148500923.issue6208@psf.upfronthosting.co.za>
In-reply-to
Content
As noted above, it's still not clear the change *can* be implemented at the standard library level - we don't have the context to determine if a Windows native path or a POSIX path is more appropriate when a Windows build is being used in a POSIX environment.
From the interpreter's point of view, the launch environment makes no difference, the only thing that matters is the target platform for the build. If they don't match, you're going to get weird glitches like this.
History
Date User Action Args
2013年11月13日 13:56:48ncoghlansetrecipients: + ncoghlan, terry.reedy, eric.smith, tim.golden, ThurnerRupert, r.david.murray, BreamoreBoy, laurent.birtz
2013年11月13日 13:56:48ncoghlansetmessageid: <1384351008.08.0.372148500923.issue6208@psf.upfronthosting.co.za>
2013年11月13日 13:56:48ncoghlanlinkissue6208 messages
2013年11月13日 13:56:47ncoghlancreate

AltStyle によって変換されたページ (->オリジナル) /