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 docs@python, gronke, paul.moore, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2017-09-25.16:18:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506356307.74.0.345575993967.issue31569@psf.upfronthosting.co.za>
In-reply-to
Content
I'm okay with the PR as it stands, especially the parts that affect GitHub and appveyor, as those are almost certainly using case sensitive comparisons.

It's definitely not easier to update the case of a file that is in git, and doing so will very likely break users (we had to do a case-folding pass over the Mercurial repository because while it could handle case changes, git could not import the ones we had in history).

Personally I'd prefer it to have always been PCBuild rather than PCbuild, and it's very likely that I've introduced most of the 'incorrect' ones. But what's done is done and we should avoid the potential distraction of mismatched case throughout the rest of our codebase.
History
Date User Action Args
2017-09-25 16:18:27steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, docs@python, zach.ware, serhiy.storchaka, gronke
2017-09-25 16:18:27steve.dowersetmessageid: <1506356307.74.0.345575993967.issue31569@psf.upfronthosting.co.za>
2017-09-25 16:18:27steve.dowerlinkissue31569 messages
2017-09-25 16:18:27steve.dowercreate