[issue19338] multiprocessing: sys.exit() from a child with a non-int exit code exits with 0

2013-10-21 Thread Brodie Rao
Changes by Brodie Rao : -- nosy: +jnoller, sbt ___ Python tracker <http://bugs.python.org/issue19338> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue19338] multiprocessing: sys.exit() from a child with a non-int exit code exits with 0

2013-10-21 Thread Brodie Rao
Brodie Rao added the comment: Here's the patch for 3.3. -- keywords: +patch Added file: http://bugs.python.org/file32286/multiprocessing-sys-exit-3.3.patch ___ Python tracker <http://bugs.python.org/is

[issue19338] multiprocessing: sys.exit() from a child with a non-int exit code exits with 0

2013-10-21 Thread Brodie Rao
Changes by Brodie Rao : Added file: http://bugs.python.org/file32287/multiprocessing-sys-exit-2.7.patch ___ Python tracker <http://bugs.python.org/issue19338> ___ ___

[issue19338] multiprocessing: sys.exit() from a child with a non-int exit code exits with 0

2013-10-21 Thread Brodie Rao
New submission from Brodie Rao: Normally: $ python >>> import sys >>> sys.exit('foo') foo $ echo $? 1 However, with multiprocessing: >>> import sys >>> from multiprocessing import Process >>> p = Process(ta

[issue9661] 2to3 except fixer does the wrong thing for certain raise statements

2010-08-22 Thread Brodie Rao
New submission from Brodie Rao : Given the following statements: raise Foo('bar'), None, baz raise Foo('bar'), None 2to3 produces: raise Foo('bar')(None).with_traceback(baz) raise Foo('bar')(None) Instead of: raise Foo('

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

2009-06-01 Thread Brodie Rao
Changes by Brodie Rao : -- nosy: +brodie ___ Python tracker <http://bugs.python.org/issue6154> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue4050] inspect.findsource() returns binary data for shared library modules

2008-10-05 Thread Brodie Rao
New submission from Brodie Rao <[EMAIL PROTECTED]>: Calling inspect.findsource() on a module whose __file__ attribute points to a shared library causes findsource() to return the binary's data: >>> import time >>> time.__file__ '/System/Library/Frameworks

[issue3684] traceback.format_exception_only() misplaces the caret for certain SyntaxErrors

2008-08-25 Thread Brodie Rao
New submission from Brodie Rao <[EMAIL PROTECTED]>: >> + File "", line 1 + ^ SyntaxError: invalid syntax >>> import sys >>> import traceback >>> traceback.print_exception(sys.last_type, sys.last_value, None) File "

[issue3242] Segfault in PyFile_SoftSpace/PyEval_EvalFrameEx with sys.stdout reassigned

2008-07-01 Thread Brodie Rao
Brodie Rao <[EMAIL PROTECTED]> added the comment: Thanks. The patch fixes the crash for me on Python 2.5.2 and 2.6b1 on OS X and Python 2.4.5 on Debian and Ubuntu. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3242] Segfault in PyFile_SoftSpace/PyEval_EvalFrameEx with sys.stdout reassigned

2008-06-30 Thread Brodie Rao
Brodie Rao <[EMAIL PROTECTED]> added the comment: Running with Python 2.5.2 with guard malloc on OS X 10.5 produces a similar crash to that of Python 2.4 on Linux: (gdb) set env DYLD_INSERT_LIBRARIES /usr/lib/libgmalloc.dylib (gdb) run ~/Documents/Code/py-crash/crash5.py Starting p

[issue3242] Segfault in PyFile_SoftSpace/PyEval_EvalFrameEx with sys.stdout reassigned

2008-06-30 Thread Brodie Rao
Brodie Rao <[EMAIL PROTECTED]> added the comment: Using Python 2.5.2 from python.org on Mac OS X 10.5, I get the same error: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0xad40 0x0052ed30 in ?? () (gdb) bt #0 0x0052ed30 in ?? () #1 0x0002a

[issue3242] Segfault in PyFile_SoftSpace/PyEval_EvalFrameEx with sys.stdout reassigned

2008-06-30 Thread Brodie Rao
Brodie Rao <[EMAIL PROTECTED]> added the comment: Actually, I've tested this script on another Debian x86 machine and two Ubuntu x86 machines, all which exhibit the exact same crash with their Python 2.4 distributions. I don't think it's a hardware issue, I think there

[issue3242] Segfault in PyFile_SoftSpace/PyEval_EvalFrameEx with sys.stdout reassigned

2008-06-29 Thread Brodie Rao
Brodie Rao <[EMAIL PROTECTED]> added the comment: Actually, this seems to be a hardware issue, despite the consistency between runs and the duplication on another machine. I think you can ignore/close this bug. Sorry for the noise. ___ Python t

[issue3242] Segfault in PyFile_SoftSpace/PyEval_EvalFrameEx with sys.stdout reassigned

2008-06-29 Thread Brodie Rao
New submission from Brodie Rao <[EMAIL PROTECTED]>: Running the attached script - which reassigns sys.stdout to an object that proxies sys.stdout, and eventually reassigns it back to the original object - using Apple's distribution of Python 2.5.1 on an x86 machine, I get the foll

[issue2856] os.listdir doc should mention that Unicode decoding can fail

2008-05-14 Thread Brodie Rao
New submission from Brodie Rao <[EMAIL PROTECTED]>: The documentation for os.listdir should mention that there's a possibility that it can fail to decode paths to unicode objects and that it returns str objects for those paths it couldn't decode. The documentation should a

[issue2476] optparse docs should mention %default being new in 2.4

2008-03-24 Thread Brodie Rao
New submission from Brodie Rao <[EMAIL PROTECTED]>: The %default option help string feature doesn't exist in Python 2.3, but the documentation for Python 2.4 and 2.5 don't mention that it was added in 2.4. It should mention this so people developing for 2.3 and 2.4/2.5 can