New submission from Vinay Sajip vinay_sa...@yahoo.co.uk:
test_codecs has started failing on Windows: I can't tell if the problem is in
the tests.
== CPython 3.3.0a0 (default, Nov 8 2011, 22:34:51) [MSC v.1500 32 bit (Intel)]
== Windows-7-6.1.7600 little-endian
==
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
FWIW, stack trace from VS 2008:
python33.dll!_PyLong_New(int size=0x0002) Line 145 C
python33.dll!PyLong_FromLong(long ival=0x81b6) Line 210 + 0x7
bytesC
STINNER Victor victor.stin...@haypocalc.com added the comment:
I may be related to recent changes on codecs. My following commit fixed a
test_codecs crash, but there is maybe another bug.
changeset: 73466:9042d71962d6
user:Victor Stinner victor.stin...@haypocalc.com
date:Wed
STINNER Victor victor.stin...@haypocalc.com added the comment:
The test doesn't crash on our Windows buildbots. Please try to update. If the
problem does still exist, reopen the issue.
--
resolution: - fixed
status: open - closed
___
Python tracker
Martin v. Löwis mar...@v.loewis.de added the comment:
Why was the change necessary? unicode_decode_call_errorhandler shouldn't be
called with WSTR strings (i.e. it is only intended to support ready strings).
--
___
Python tracker
STINNER Victor victor.stin...@haypocalc.com added the comment:
Why was the change necessary?
First because unicode_decode_call_errorhandler() was called with the wrong
argument count:
1.90 -v, outpos, out))
1.91 +v, outpos))
