[issue6460] test failure in test_xmlrpc on Gentoo in trunk

Kristján Valur Jónsson added the comment: This is probably a race condition, where the server thread hasn't updated the stats yet when the client is testing them. I'm so used to work with non-preemtive scheduling in stackless python that I sometimes forget how threads work :) I submitted rev

[issue6358] os.popen exit code inconsistent

Amaury Forgeot d'Arc added the comment: Added a few tests, and fixed in r73934 (py3k) and r73935 (3.1) Thanks for the report! -- nosy: +amaury.forgeotdarc resolution: -> fixed status: open -> closed ___ Python tracker

[issue6459] Lib/distutils\tests\test_build_ext.py fails on VC6

Amaury Forgeot d'Arc added the comment: Confirmed with vs2008. I wonder why the buildbots don't fail. -- nosy: +amaury.forgeotdarc ___ Python tracker ___

[issue6446] import_spam() in extending python can fail without setting the error.

Georg Brandl added the comment: Thanks, fixed in r73938. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue6448] imp.find_module() -- be explicity that 'path' must be a list

Georg Brandl added the comment: I reworded the paragraph a bit in r73939. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue6459] Lib/distutils\tests\test_build_ext.py fails on VC6

Tarek Ziadé added the comment: Thanks for the patch, I'll integrate asap. Notice that I run the tests under windows but without a full range of VC versions, so I count a lot on the buildbots to show me these kind of failures. -- priority: -> normal resolution: -> accepted __

[issue6430] array.array falsely advertises support for 'w' in documentation

Georg Brandl added the comment: OK, fixed this in r73940, r73941, r73942. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue6421] errors in docs re module initialization vs self arg to functions

Georg Brandl added the comment: Fixed both instances in r73943. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue1921] Confusing Descrintro example

Changes by Georg Brandl : -- assignee: georg.brandl -> gvanrossum nosy: +gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing

[issue6459] Lib/distutils\tests\test_build_ext.py fails on VC6

Tarek Ziadé added the comment: Mmm, also notice that the current build_ext trunk uses "init" in the code, which means that the "PyInit" prefix was added on py3k but not backported in the trunk. So i'll fix that too -- ___ Python tracker

[issue6456] locale.D_* and .T_* are int, not string

Georg Brandl added the comment: I moved the constants' description into the nl_langinfo() description and clarified their use in r73945. -- resolution: -> fixed status: open -> closed ___ Python tracker __

[issue6269] threading documentation makes no mention of the GIL

Changes by Georg Brandl : -- assignee: georg.brandl -> jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue6459] distutils.command.build_ext.get_export_symbols should use the "PyInit" prefix rather then "init"

Tarek Ziadé added the comment: The bug also exists in 2.6 so I'm backporting the fix -- title: Lib/distutils\tests\test_build_ext.py fails on VC6 -> distutils.command.build_ext.get_export_symbols should use the "PyInit" prefix rather then "init" versions: +Python 2.6, Python 2.7

[issue6459] distutils.command.build_ext.get_export_symbols should use the "PyInit" prefix rather then "init"

Tarek Ziadé added the comment: done in r73946, r73947 (2.6), r73948 (py3k), r73949 (3.1) Thanks ! (also, the build_ext module is now perfectly similar between 2.x and 3.x) -- status: open -> closed ___ Python tracker

[issue6459] distutils.command.build_ext.get_export_symbols should use the "PyInit" prefix rather then "init"

Hirokazu Yamamoto added the comment: Well, I'm not sure but for example, Modules/_randomemodule.c uses "init_random" on trunk. Is it OK to use "PyInit" on trunk too? -- ___ Python tracker _

[issue6459] distutils.command.build_ext.get_export_symbols should use the "PyInit" prefix rather then "init"

Tarek Ziadé added the comment: What's the logic behind PyInit_ ? For instance Modules/_bsddb.c uses PyInit, so does Modules/zlibmodule.c -- status: closed -> open ___ Python tracker __

[issue6459] distutils.command.build_ext.get_export_symbols should use the "PyInit" prefix rather then "init"

Hirokazu Yamamoto added the comment: bsddb seems to use #if directive to switch function name. ("init_bsddb" on trunk) #if (PY_VERSION_HEX < 0x0300) DL_EXPORT(void) init_bsddb(void) #else PyMODINIT_FUNC PyInit__bsddb(void)/* Note the two underscores */ #endif And zlibmodule.c, there

[issue3982] support .format for bytes

Arjen Nienhuis added the comment: There are many binary formats that use ASCII numbers. 'HTTP chunking' uses ASCII mixed with binary (octets). With 2.6 you could write: def chunk(block): return b'{0:x}\r\n{1}\r\n'.format(len(block), block) With 3.0 you'd have to write this: def chunk(bl

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

R. David Murray added the comment: OK, the test passes on my box now. But from the way the test is phrased it sounds like there is still a small risk that the test will fail in unusual timing circumstances? -- ___ Python tracker

[issue3982] support .format for bytes

Martin v. Löwis added the comment: > def chunk(block): > return format(len(block), 'x').encode('ascii') + b'\r\n' + block + > b'\r\n' > > You cannot convert to ascii at the end of the pipeline as there are > bytes > 127 in the data blocks. I wouldn't write it in such a complicated way. Ins

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

R. David Murray added the comment: By the way, although my system doesn't show it, the Gentoo 3.x buildbot shows the error. I'm sure you were going to forward port the patch anyway :) -- ___ Python tracker ___

[issue3982] support .format for bytes

Arjen Nienhuis added the comment: > def chunk(block): >   return hex(len(block)).encode('ascii') + b'\r\n' + block + b'\r\n' hex(10) returns '0xa' instead of 'a'. > This doesn't need any format call, and describes adequatly how the > protocol works: send an ASCII-encoded hex length, send CRLF,

[issue6462] bsddb3 intermittent test failures

New submission from R. David Murray : The buildbots periodically report failures in the bsddb3 test suite. These are not reproducible and presumably are timing-based. It would be best if the tests could be made to pass consistently, to make the buildbot output more useful. Here is one such fai

[issue1921] Confusing Descrintro example

Guido van Rossum added the comment: I'm guessing you weren't ready for learning about metaclasses if you didn't get the fact that 'name' was the loop control variable in the two different loops. The example is only 11 lines long! Still, I'm fine with the two suggested renames. I'm not fine wi

[issue3982] support .format for bytes

Martin v. Löwis added the comment: > hex(10) returns '0xa' instead of 'a'. Ah, right. So I would still use '{0:x}'.format(100).encode("ascii") rather than the format builtin format function. Actually, I would probably use ('%x' % len(bytes)).encode("ascii") > The point is that need to

[issue6459] distutils.command.build_ext.get_export_symbols should use the "PyInit" prefix rather then "init"

Georg Brandl added the comment: The "PyInit_" prefix is only to be used in Python 3, it is part of PEP 3121. Please revert changes to trunk/2.6 that assume the "PyInit_" name. -- nosy: +georg.brandl ___ Python tracker

[issue6459] distutils.command.build_ext.get_export_symbols should use the "PyInit" prefix rather then "init"

Tarek Ziadé added the comment: Thanks for the explanation, I've reverted the change on 2.x. -- status: open -> closed versions: -Python 2.6, Python 2.7 ___ Python tracker ___ __

[issue6463] IDLE with Tk-Cocoa: Edit, format menus hang

New submission from Kevin Walzer : In running IDLE against a build of Tk-Cocoa (8.5.7) on OS X, the edit and format menus sometimes hang and require a force-quit of IDLE. This happens when I try to paste text, and also when trying to format selections of text with indentation, etc. I've looked

[issue6464] test_normalization failures due to truncated NormalizationTest.txt file

New submission from R. David Murray : I worked for a while tracking down a mysterious failure in test_normalization on my machine. I eventually discovered that a clean checkout did not exhibit the problem. A distclean on my original checkout did not fix the problem. By doing a diff I finally f

[issue6464] test_normalization failures due to truncated NormalizationTest.txt file

Changes by R. David Murray : -- nosy: +lemburg, loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue6440] 2to3: convert deprecated string.maketrans to str.maketrans

Changes by Benjamin Peterson : -- resolution: -> rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue6465] email.feedparser regular expression bug (NLCRE_crack)

New submission from jkg : If the parser is fed a chunk which ends with '\r' and the next chunk begins with '\n', it incorrectly parses this into a line ending with '\r' and an empty line ending with '\n' instead of a single line ending with '\r\n'. Test attached. Patch to follow. -- com

[issue6465] email.feedparser regular expression bug (NLCRE_crack)

jkg added the comment: Patch. -- keywords: +patch Added file: http://bugs.python.org/file14485/nlcre.patch ___ Python tracker ___ ___

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

Kristján Valur Jónsson added the comment: No, this should take care of it. In order for the client side request to succeed, the server must have cycled through the previous request and updated its statistic. It is only the statistic for the final request tha t may be missed. And yes, I was

[issue6460] test failure in test_xmlrpc on Gentoo in trunk

Kristján Valur Jónsson added the comment: merged testsuite fix to py3k in revision 73961 -- ___ Python tracker ___ ___ Python-bugs-lis

[issue1921] Confusing Descrintro example

Benjamin Peterson added the comment: I've now updated the website to Guido's new code. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue6464] test_normalization failures due to truncated NormalizationTest.txt file

R. David Murray added the comment: Benjamin fixed this in r73962 by having the test support routine put the files in Lib/test/data, and adding a rule to the distclean target to empty that directory. -- nosy: +benjamin.peterson status: open -> closed

[issue6464] test_normalization failures due to truncated NormalizationTest.txt file

Changes by Benjamin Peterson : -- resolution: -> fixed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m