[issue2388] Compiler warnings when using UCS4

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: This is now fixed in r62199 -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2388] Compiler warnings when using UCS4

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: This is because in UCS, Py_UNICODE is an unsigned long. In calls to PyErr_Format, the format specifier %c (int, the UCS2 Py_UNICODE) is given, so the compiler gives a warning. -- versions: -Python 3.0

[issue2388] Compiler warnings when using UCS4

Christian Heimes <[EMAIL PROTECTED]> added the comment: I'll check it out later. I haven't been testing UCS4 builds for more than a month. -- assignee: -> tiran keywords: +easy nosy: +tiran priority: -> high __ Tracker <[EMAIL PROTECTED]>

[issue2388] Compiler warnings when using UCS4

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: There are similar warnings in formater_unicode.c: In file included from Python/formatter_unicode.c:13: Python/../Objects/stringlib/formatter.h: In function 'unicode__format__': Python/../Objects/stringlib/formatter.h:789: warning: format '%

[issue2388] Compiler warnings when using UCS4

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: This is MacOS 10.4, Apple gcc 4.0.1, and revision 61518. __ Tracker <[EMAIL PROTECTED]> __ ___ P

[issue2388] Compiler warnings when using UCS4

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: What operating system/compiler? Both branches? What precise revisions? -- nosy: +loewis __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2388] Compiler warnings when using UCS4

New submission from Benjamin Peterson <[EMAIL PROTECTED]>: Compiling Python with --enable-unicode=ucs4 yields some compiler warnings for unicodeobject.c: In file included from Objects/unicodeobject.c:7807: Objects/stringlib/string_format.h: In function 'do_conversion': Objects/stringlib/string_fo