Erik Bray <erik.m.b...@gmail.com> added the comment:

Well, I agree there's an unfortunate trade-off here: One can skip the test, 
allowing the test suite to work on slightly older versions of Cygwin, from 
before this issue was fixed.  However, I then lose regression testing on newer 
versions.  My personal feeling in this case is that it's not a very important 
test and can be skipped in the future (although the bug that this test caught 
was fairly serious and one would want regression testing for it...)

As an alternative I could be more fine-grained and only skip the test on older 
versions of Cygwin that are affected.  I was hoping to avoid putting in too 
much Cygwin-specific test utilities, though adding a version check for Cygwin 
is not terribly hard (I do the same for my Cygwin port of psutil).

For reference, the current version of Cygwin that comes installed on AppVeyor 
(for which I'm trying to get a Cygwin build set up) is 2.8.0, which *is* (just 
barely) affected by this bug.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue31883>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to