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 paul.moore
Recipients docs@python, gronke, paul.moore, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2017-09-24.12:37:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I would strongly prefer the docs to be changed to match the implementation rather than the other way round. However, I don't see the use case for this - what case sensitive filesystem would anybody be building the Windows version of Python on?

I'm -1 on changing the actual build scripts, as that introduces risk for no actual benefit. I'm +0 on changing the docs, assuming it's possible to make things consistent with a doc-only change. But I can't imagine anyone reading those docs would expect a filesystem to be case sensitive, so I doubt it would matter in practice.
Date User Action Args
2017-09-24 12:37:51paul.mooresetrecipients: + paul.moore, tim.golden, docs@python, zach.ware, serhiy.storchaka, steve.dower, gronke
2017-09-24 12:37:51paul.mooresetmessageid: <>
2017-09-24 12:37:51paul.moorelinkissue31569 messages
2017-09-24 12:37:51paul.moorecreate