From: <fwi...@gm...> - 2012-12-12 00:09:46
|
On Sun, Dec 9, 2012 at 1:32 PM, Jeff Allen <ja...py...@fa...> wrote: > I've ventured a little way down the road of a possible solution. I think I > could make Jython behave the same as CPython, and remove the concessions and > skips that allow us to get away with the divergence, by removing or > re-thinking these tests. Each operation has its nuances to be dealt with > case by case, but that's the essence of it. > > Quite a few of these checks are in io.FileIO and ancestors, rather than > _io.PyFileIO. I'm trying to change the former as little as I can, but this > would change nearly every method (in a small way). Does anyone (Philip > particularly) foresee impacts to other code that I might not notice in > testing? Philip would be best at answering here, but I for one am very glad you are having a look at this. Every little bit of compatibility helps. BTW I'm not at all sure that this is relevant to the exact issue you are looking at, but just in case you hadn't seen it, the OS and IO exception hierarchy got an overhaul in 3.3: http://docs.python.org/3/whatsnew/3.3.html#pep-3151-reworking-the-os-and-io-exception-hierarchy Thanks again for looking at these issues! -Frank |