Michael Witten added the comment:
* Bugs, by their very nature, are often obscure; some of the worst
in history have lain dormant, unseen, for years or perhaps even
decades.
Unsurprisingly, then, this bug is also a corner case that would be
unknowingly triggered in practice only rarely
Michael Witten added the comment:
* This is not a feature request;
this is a bug fix for errant behavior.
However, in the interest of civility, I have not re-opened this issue.
* > Python 2.7 DOES NOT support filesystem semantics that differ
> from the "default" semant
Michael Witten added the comment:
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
Michael Witten added the comment:
Thank you for the reply.
* As already stated, I believe that Python 3
is not affected by this problem; certainly,
version 3.5.2 does not seem to be affected,
as per my ad hoc testing.
* Very many programs are targeted to Python 2.7,
and probably
Michael Witten added the comment:
I've attached as `pep-235-on-posix.patch' a copy of `pep-235-on-posix.export',
in order to see whether that helps the system recognize the content as a patch.
I'm loath to rename the original upload, because I'm not able to edit my
original comment to reflect
New submission from Michael Witten:
The attached file, `pep-235-on-posix.export', contains 3 patches; the file
includes the intended commit messages and authorship information. To apply
these patches, save the file to:
/path/to/pep-235-on-posix.export
and then run the following from within
Michael Witten [EMAIL PROTECTED] added the comment:
Apparently, it might affect all CodecInfo objects:
class CodecInfo(tuple):
def __new__(cls, encode, decode, streamreader=None,
streamwriter=None,
incrementalencoder=None, incrementaldecoder=None, name=None):
self = tuple
