|Priority:||4 - Normal|
|Created by:||Bryan Cantrill [X]|
|Reported by:||Bryan Cantrill [X]|
|Assigned to:||Bryan Cantrill [X]|
Won't Fix: The problem described is an issue which will never be fixed.
(Resolution Date: 2015-03-11T16:25:39.000Z)
See OS-4014 and OS-4015 for test suite details.
So as it turns out, this test is failing because it's finding that /dev/tty is seekable. It's unclear why this is being tested for -- it's very obscure (and irrelevant) implementation-defined behavior that already varies from system to system. Here's the test code in question:
if sys.platform != "win32": try: f = _FileIO("/dev/tty", "a") except EnvironmentError: # When run in a cron job there just aren't any # ttys, so skip the test. This also handles other # OS'es that don't support /dev/tty. pass else: self.assertEqual(f.readable(), False) self.assertEqual(f.writable(), True) if sys.platform != "darwin" and \ 'bsd' not in sys.platform and \ not sys.platform.startswith('sunos'): # Somehow /dev/tty appears seekable on some BSDs self.assertEqual(f.seekable(), False) self.assertEqual(f.isatty(), True) f.close()
Given that no app can reasonably depend on the fact that /dev/tty is seekable on us (and not seekable on Linux) and given that fixing this is unlikely to come at zero cost or risk, I'm closing this out as Won't Fix -- we can reevaluate in the (unlikely) event that an app finds a way to trip on this.