STINNER Victor victor.stin...@haypocalc.com added the comment:
Backported in r79197 (2.6).
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7820
STINNER Victor victor.stin...@haypocalc.com added the comment:
Commited: r78603 (trunk), r78608 (py3k), r78609 (3.1).
Delay the fix in 2.6 after the release of 2.6.5. This issue is far from being
critical, I don't want to introduce a regression after an RC :-)
--
Benjamin Peterson benja...@python.org added the comment:
I think the test should be in test_pep263.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7820
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
I think the test should be in test_pep263.
Right! I always hesitate when adding a new test.
--
Added file: http://bugs.python.org/file16072/parser_restore_bom-3.patch
___
Python tracker
Changes by STINNER Victor victor.stin...@haypocalc.com:
Removed file: http://bugs.python.org/file16068/parser_restore_bom-2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7820
___
New submission from STINNER Victor victor.stin...@haypocalc.com:
My patch fixes check_bom() to restore all bytes in the right order if there is
no BOM to leave the stream unchanged and to fix an assertion error in
buf_ungetc() (raised in pydebug mode).
The current code only unget one byte
Benjamin Peterson benja...@python.org added the comment:
Are there test cases for this?
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7820
___
Changes by STINNER Victor victor.stin...@haypocalc.com:
Added file: http://bugs.python.org/file16068/parser_restore_bom-2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7820
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
Are there test cases for this?
Here you have.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7820
___
