Andrew Bergbahamutzero8...@gmail.com writes:
Since Python 2.5, the errno attribute maps the Windows error to error
codes that match the attributes of module errno.
Good point, I completely misread that. At least the Windows error code
is still available as the winerror attribute.
As an
On 20/05/2011 18:56, Andrew Berg wrote:
This is probably somewhat off-topic, but where would I find a list of
what each error code in WindowsError means?
Assuming it's a Win32 error code, winerror.h from the Platform SDK holds
the answer. One version is linked below, it's in theory out of
With 3.2 on winxp, that is what I get with StringIO, text file, and
bytes file (the first two with b's removed). I would expect the same on
any system. If you get anything different, I would consider it a bug
Thanks Terry, you're entirely right there; I trimmed down my test case,
asked for
On 12/05/2011 20:44, Terry Reedy wrote:
I want people to know that with a simple, minimal, easy to run and
reproduce and think about test case posted, more info, more test cases,
and probable fixes were posted within an hour. (Fixes are not always
that quick, but stripping away irrelevancies
New submission from Genstein python...@genstein.net:
Reporting this as requested by Antoine Pitrou: Under certain circumstances in
Python 3.2 (r32:88445) it's possible for buffered I/O to lose data before it is
written and/or return the wrong results when reading. I tripped over this issue
Hey all,
Apologies if this is a dumb question (self = Python noob), but under
py3k is it necessary to flush() a file between read/write calls in order
to see consistent results?
I ask because I have a case under Python 3.2 (r32:88445) where it does
appear to be, on both Gentoo Linux and
On 11/05/2011 19:24, Terry Reedy wrote:
writing and reading. If you want others to look at this more, you should
1) produce a minimal* example that demonstrates the questionable
behavior, and 2) show the comparative outputs that raise your question.
Thanks for a quick response. Perhaps I was
