Nir Aides <n...@winpdb.org> added the comment: If the sequence of readaheads is ['a\r', '\nb\n'], the first use of the pattern will consume 'a', then the peek(2) will trigger a read() and the next use of the pattern will consume '\r\n'.
I updated the patch and enhanced a little the inline comments to clear this up and added the suggested test. I also ventured into a rewrite of the read() function since it seems to contain various latent bugs / problems, probably the result of ages of slow refactoring. For example, decompressor flush() depends on self.eof flag which is never set and the decrypter is fed by the raw buffer which is in turn set by the decompresser, thus theoretically feeding decrypted data back to the decrypter. I also made it completely buffered so now small reads are significantly faster. If this patch is good, i'll prepare a patch for python 3.x and 2.6 ---------- Added file: http://bugs.python.org/file15822/zipfile_7610_py27.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7610> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
