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(target=lambda: sys.exit('foo'))
p.start()
foo
p.join()
p.is_alive
Changes by Brodie Rao j...@dackz.net:
Added file: http://bugs.python.org/file32287/multiprocessing-sys-exit-2.7.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19338
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 rep...@bugs.python.org
http://bugs.python.org/issue19338
Changes by Brodie Rao j...@dackz.net:
--
nosy: +jnoller, sbt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19338
___
___
Python-bugs-list mailing
New submission from Brodie Rao j...@dackz.net:
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('bar').with_traceback(baz)
raise
Changes by Brodie Rao j...@dackz.net:
--
nosy: +brodie
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6154
___
___
Python-bugs-list mailing list
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/Python.framework/Versions/2.5/lib/python2.5
New submission from Brodie Rao [EMAIL PROTECTED]:
+
File stdin, line 1
+
^
SyntaxError: invalid syntax
import sys
import traceback
traceback.print_exception(sys.last_type, sys.last_value, None)
File stdin, line 1
+
^
SyntaxError: invalid syntax
sys.last_value
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.python.org/issue3242
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 following crash
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 tracker [EMAIL
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's a legitimate issue here
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 0x0002ad41
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 program: /Users
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 also explain when
15 matches
Mail list logo
