Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: This is a duplicate of issue1394612, which was closed as "invalid". See the discussion there:
- "in standard C mixing reads with writes yields undefined behavior [...] If you want defined behavior, then, for example, add >>> f.seek(0) between your write() and read() calls.""" BTW, python 3.0 has a new implementation of the I/O stack, which does not use fopen, and does not have this problem. ---------- nosy: +amaury.forgeotdarc resolution: -> wont fix status: open -> closed __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2730> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
