[issue38710] unsynchronized write pointer in io.TextIOWrapper in 'r+' mode

Martin Panter added the comment: Previously Issue 12215 and a couple of other duplicates were opened about this. Writing after reading with TextIOWrapper doesn't work as people expect. The report was closed apparently because Victor thought there wasn't enough interest in it. FWIW the

[issue38710] unsynchronized write pointer in io.TextIOWrapper in 'r+' mode

Change by Josh Rosenberg : -- nosy: +josh.r ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38710] unsynchronized write pointer in io.TextIOWrapper in 'r+' mode

Change by Josh Rosenberg : -- components: +Library (Lib) ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38710] unsynchronized write pointer in io.TextIOWrapper in 'r+' mode

New submission from Manuel Ignacio Pérez Alcolea : There seems to be a bug in the `io.TextIOWrapper` class while working in 'r+' mode, although I can't say the source of the problem is right there. The write pointer doesn't match `file.tell()` after performing a read operation. For example,