[issue1636] Execfile unable to take arguments beyond 255!

2007-12-16 Thread Martin v. Löwis
Martin v. Löwis added the comment: Can you please be more specific? What code exactly are you executing, and what is the exact error message that you get? In the entire Python source code, the error message Execfile unable to take arguments beyond 255! is never produced. Very few error messages

[issue1519638] Unmatched Group issue

2007-12-16 Thread Brandon Mintern
Brandon Mintern added the comment: This is still a problem which has just given me a headache, because using re.sub now requires gymnastics instead of just using a simple string as I did in Perl. -- nosy: +BMintern _ Tracker [EMAIL PROTECTED]

[issue1637] urlparse.urlparse misparses URLs with query but no path

2007-12-16 Thread John Nagle
New submission from John Nagle: urlparse.urlparse will mis-parse URLs which have a / after a ?. sa1 = 'http://example.com?blahblah=/foo' sa2 = 'http://example.com?blahblah=foo' print urlparse.urlparse(sa1) ('http', 'example.com?blahblah=', '/foo', '', '', '') # WRONG print

[issue1600] str.format() produces different output on different platforms (Py30a2)

2007-12-16 Thread Mark Summerfield
Mark Summerfield added the comment: On 2007-12-15, Christian Heimes wrote: Christian Heimes added the comment: Mark Summerfield wrote: It seems to me that Python should provide consistent results across platforms wherever possible and that this is a gratuitous inconsistency that makes

[issue1638] %zd configure test fails on Linux

2007-12-16 Thread Hrvoje Nikšić
New submission from Hrvoje Nikšić: The printf(%zd, ...) configure test fails on Linux, although it supports the %zd format. config.log reveals that the test tests for %zd with Py_ssize_t, which is (within the test) typedeffed to ssize_t. But the appropriate system header is not included by the

[issue1638] %zd configure test fails on Linux

2007-12-16 Thread Christian Heimes
Christian Heimes added the comment: I fixed the bug in r59533 trunk with a modified patch: #ifdef HAVE_SYS_TYPES_H #include sys/types.h #endif Should it be backported to 2.5? It will be merged into 3.0 automatically. -- nosy: +tiran priority: - normal resolution: - fixed status:

[issue1638] %zd configure test fails on Linux

2007-12-16 Thread Martin v. Löwis
Martin v. Löwis added the comment: I think it should be backported. -- nosy: +loewis __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1638 __ ___ Python-bugs-list mailing

[issue1638] %zd configure test fails on Linux

2007-12-16 Thread Hrvoje Nikšić
Hrvoje Nikšić added the comment: Thanks for the quick review. I considered guarding the include with #ifdef as well, but I concluded it's not necessary for the following reasons: 1. a large number of existing tests already simply include sys/types.h (the makedev test, sizeof(off_t) test,

[issue1632] email cannot be imported

2007-12-16 Thread Wubbulous
Wubbulous added the comment: I have attempted the following separately: import email import email.Utilsimport email.utils they each return the error: Traceback (most recent call last): File C:\Panda3D-1.4.2\python\lib\smtplib.py, line 49, in ? from email.base64MIME import encode

[issue1600] str.format() produces different output on different platforms (Py30a2)

2007-12-16 Thread Mark Summerfield
Mark Summerfield added the comment: On 2007-12-15, Christian Heimes wrote: Christian Heimes added the comment: Mark Summerfield wrote: It seems to me that Python should provide consistent results across platforms wherever possible and that this is a gratuitous inconsistency that makes

[issue1636] Execfile unable to take arguments beyond 255!

2007-12-16 Thread Jack Atkinson
Jack Atkinson added the comment: Error message from ipython console: In [28]: mibBuilder2 = builder.MibBuilder().loadModules('ADTRAN-TC') --- class 'pysnmp.smi.error.SmiError' Traceback (most recent call last)

[issue1722225] Build on QNX

2007-12-16 Thread Vladimir Konjkov
Vladimir Konjkov added the comment: willing you implement thread support for qnx6, or may be qnx4? _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue175 _ ___

[issue1621] Python should compile with -Wstrict-overflow when using gcc

2007-12-16 Thread Alexandre Vassalotti
Alexandre Vassalotti added the comment: I compiled Python using gcc 4.3.0 with the -Wstrict-overflow, and that's the only warning I got: Objects/doubledigits.c: In function ‘_PyFloat_Digits’: Objects/doubledigits.c:313: error: assuming signed overflow does not occur when assuming that (X + c)