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 laurent.birtz
Recipients BreamoreBoy, ThurnerRupert, eric.smith, laurent.birtz, ncoghlan, r.david.murray, terry.reedy, tim.golden
Date 2013-11-12.17:34:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384277654.85.0.996843052804.issue6208@psf.upfronthosting.co.za>
In-reply-to
Content
In my opinion, the decision to cross your arms and pretend there is no issue is unprofessional.

Summary of your arguments:
- It's Microsoft's fault.
- Windows accepts backslashes anyway.
- Shell detection is difficult.
- It's a complex issue.

None of this is relevant to addressing the issue ThurnerRupert was facing. He asked to be able to CONFIGURE the path seperator. This needs not involve shell detection (which is indeed brittle). This could be handled simply by the user setting 'os.sep' and having os.path.join() and friends use that.

I'm using SCons on MinGW and the build is failing due to the messed-up paths.

<rant>
I'm less than thrilled about learning that this won't get fixed. I feel that one of the important strength of Python is that it "just works" on many platforms and this amply justifies this issue not being treated with such frivolity.
</rant>
History
Date User Action Args
2013-11-12 17:34:14laurent.birtzsetrecipients: + laurent.birtz, terry.reedy, ncoghlan, eric.smith, tim.golden, ThurnerRupert, r.david.murray, BreamoreBoy
2013-11-12 17:34:14laurent.birtzsetmessageid: <1384277654.85.0.996843052804.issue6208@psf.upfronthosting.co.za>
2013-11-12 17:34:14laurent.birtzlinkissue6208 messages
2013-11-12 17:34:14laurent.birtzcreate