[issue7173] Cython compiler run crashes CPython 3.1.1 and 3.2

Stefan Behnel added the comment: I hadn't, but it looks like the 2to3-ed Cython also runs on 3.0 now, so I tested that, but I failed to get the procedure below to crash for me. And that's both in 3.0 *and* 3.1.1! :-/ But I can still provoke the crash in 3.0, 3.0.1, 3.1.1 and the latest 3.2 when

[issue7329] global statements outside functions/methods should raise SyntaxError

Raymond Hettinger added the comment: I concur. -- nosy: +rhettinger resolution: -> rejected status: open -> closed ___ Python tracker ___ ___

[issue7373] Use PyModule_AddIntMacro() in Modules/gcmodule.c

Jon Parise added the comment: That's true. I thought it worked the same as the ADD_INT() macro I replaced, but I see that I was wrong. Given that, perhaps the original code is best. I don't see a lot of value in replacing PyModule_AddIntConstant() with PyModule_AddIntMacro() within ADD_INT().

[issue7373] Use PyModule_AddIntMacro() in Modules/gcmodule.c

Benjamin Peterson added the comment: You don't account for PyModule_AddIntMacro failing. -- nosy: +benjamin.peterson ___ Python tracker ___ __

[issue7173] Cython compiler run crashes CPython 3.1.1 and 3.2

Antoine Pitrou added the comment: Have you tried using 3.1.0 and even 3.0? -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-lis

[issue7373] Use PyModule_AddIntMacro() in Modules/gcmodule.c

Changes by Jon Parise : Added file: http://bugs.python.org/file15379/gc_macros-py3k.patch ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue7373] Use PyModule_AddIntMacro() in Modules/gcmodule.c

New submission from Jon Parise : The attached patch uses PyModule_AddIntMacro() to register the gc module's constants instead of using a local ADD_INT() macro. -- components: Interpreter Core files: gc_macros-trunk.patch keywords: patch messages: 95589 nosy: jon severity: normal status:

[issue7173] Cython compiler run crashes CPython 3.1.1 and 3.2

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue6615] multiprocessing logging support test

Jesse Noller added the comment: merged to py3k in r76439 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue7128] cPickle looking for non-existent package copyreg

Alexandre Vassalotti added the comment: Yes. But, I would remove the ugly copy_reg_str variable from cPickle as the patch. -- Added file: http://bugs.python.org/file15377/remove_copyreg_str.diff ___ Python tracker

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Guido van Rossum added the comment: I don't think it would hurt to put it back, would it? I think the "remove this in 3.1" note was made when we expected 3.1 to be happening 1.5 years after 3.0 rather than a few months. -- nosy: +gvanrossum ___ Py

[issue7372] Regression in pstats

Changes by Alexander Belopolsky : -- versions: +Python 3.1, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue6064] Add "daemon" argument to threading.Thread constructor

Ask Solem added the comment: Patch for multiprocessing, adding the daemon kwarg attached. -- nosy: +asksol Added file: http://bugs.python.org/file15376/6064-multiprocessing-daemon-kwarg.patch ___ Python tracker __

[issue6615] multiprocessing logging support test

Jesse Noller added the comment: patch committed to trunk in r76438 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue5738] multiprocessing example wrong

Jesse Noller added the comment: I've removed the example on all active branches. r76433 is the changelist -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue7272] test_multiprocessing fails consistently with 'signal 12' on FreeBSD 6.2 buildbot.

Mark Dickinson added the comment: > In any event though, I'm fine with enabling the support on the 7.2 > buildbot (I'll stick it in loader.conf so I don't have to remember after a reboot) That would be great---thank you! > if we're past any point of wanting to check how the test > behaves wit

[issue7272] test_multiprocessing fails consistently with 'signal 12' on FreeBSD 6.2 buildbot.

Mark Dickinson added the comment: > I'm not that familiar with the test harness, but would it be possible to > get test_multiprocessing to log an error when it has to be skipped. Well, there should be a skip message next to the test_multiprocessing line in the results. I'm not sure whether th

[issue5738] multiprocessing example wrong

Jesse Noller added the comment: On Sat, Nov 21, 2009 at 8:41 AM, Ask Solem wrote: > > Ask Solem added the comment: > > Are we sure this fits the scope of multiprocessing? It's a nice feature, > but such a long and complex example in the documentation is wrong IMHO, if > this is something peopl

[issue6615] multiprocessing logging support test

Changes by Ask Solem : -- keywords: +patch Added file: http://bugs.python.org/file15375/6615.patch ___ Python tracker ___ ___ Python-bu

[issue5738] multiprocessing example wrong

Ask Solem added the comment: Are we sure this fits the scope of multiprocessing? It's a nice feature, but such a long and complex example in the documentation is wrong IMHO, if this is something people need it should be implemented as a reusable solution, not as an example people copy and pas

[issue7128] cPickle looking for non-existent package copyreg

Georg Brandl added the comment: Now I'm confused. So the only thing left to do is the patch attached here? -- ___ Python tracker ___ _

[issue7285] multiprocessing module, example code error

Changes by Ask Solem : Added file: http://bugs.python.org/file15374/7285.patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc