5houston added the comment:
Yes I could. You can find it attached.
--
Added file: http://bugs.python.org/file19140/minCrashing.py.bz2
___
Python tracker
<http://bugs.python.org/issue8
5houston added the comment:
I vote for the latter.
--
___
Python tracker
<http://bugs.python.org/issue8028>
___
___
Python-bugs-list mailing list
Unsubscribe:
5houston added the comment:
If you will choose the former way, I think it would be better to write in the
"multiprocessing.Process" documentation that sys.exit is the function to use to
break the process execution inside itself, but maybe it would be better to wrap
sys.exit
5houston added the comment:
Hi.
I tried my code (minCrashing.py) in windows using python 3.1.2, 2.3alpha4 and
3.1.3rc1
The behaviour is deeply different from linux 3.1.2.
I think it's a bug.
What do you think about it?
--
versions: +Python 3.2 -Pytho
5houston added the comment:
Yes, I can.
This is the minCrashing.py output from python3.2a4 in windows XP sp3:
Traceback (most recent call last):
File "c:\Python32\lib\multiprocessing\process.py", line 233, in _bootstrap
self.run()
File "c:\Python32\lib\multiprocessing\pr
New submission from 5houston :
Try to execute "python -OO crashingMain.py" using python 3.1 or 3.1.1.
It creates and starts 5 SendingProcess(es).
SendingProcess inherits from multiprocessing.Process and
multiprocessing.queue.Queue.
Each process starts a loop.
In the meanwhil
