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 mfwitten
Recipients brett.cannon, eric.snow, mfwitten, ncoghlan, tim.peters
Date 2016-11-15.21:58:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479247138.69.0.446683007488.issue28670@psf.upfronthosting.co.za>
In-reply-to
Content
Guess what?

    Linux can access HFS+ and NTFS volumes.

Firstly, how does that fit into your ideas for testing? It doesn't;
however, you'll note that my own brief analysis did attempt to wrestle
with this nuance.

Secondly, it was (and is) clearly asinine to conflate an operating
system with a particular file system; PEP 235 betrays the naive
ways of ancient thinkers---the spirit of the text of PEP 235
has never been completely implemented, and the result of this
naivete is a broken userspace *today*.

Here are the cases for my patch:

  * Non-POSIX platforms:         Nothing changes.

  * POSIX platforms:

      * PYTHONCASEOK set:        Nothing changes.

      * PYTHONCASEOK not set:    Almost nothing changes.
                                 -----------------------
                                 Accessing an insane file
                                 system now works just like
                                 on a Non-POSIX platform. In
                                 most cases, this won't change
                                 anything; yet, rare cases
                                 will *now* Just Work, rather
                                 than crapping out with some
                                 inscrutable error.

Where is your qualm?

As for the organization of patches, what I have presented (and
especially what I describe for a merge commit) not only meets
your stated goals, but *exceeds* them in every way.

Nevertheless, I would be willing to dumb down my submission if
it meant getting this bug fixed.

----------

It's rude to close abruptly an issue without even the implicit
consent of your collocutor, especially when the reasoning for
such an action is, once again, based explicitly on a startling
degree of willful ignorance and maybe even technical incompetence.
History
Date User Action Args
2016-11-15 21:58:58mfwittensetrecipients: + mfwitten, tim.peters, brett.cannon, ncoghlan, eric.snow
2016-11-15 21:58:58mfwittensetmessageid: <1479247138.69.0.446683007488.issue28670@psf.upfronthosting.co.za>
2016-11-15 21:58:58mfwittenlinkissue28670 messages
2016-11-15 21:58:58mfwittencreate