Corey Goldberg added the comment:
note:
on Windows Vista it is not ery intermittant :)
crashes every time the program is stopped.
___
Python tracker
<http://bugs.python.org/issue5
Corey Goldberg added the comment:
little more info:
If you create a Queue in the main thread and pass this to each worker
thread, it works fine.
If you create the Queue inside the worker thread and then pass it to a
new thread, it can crash.
when it crashes, you get an immediate core dump
New submission from Corey Goldberg :
I can get the Python interpreter to core dump when running the following
code:
http://pastebin.com/f261f398f
To reproduce:
- run the above code and press ctrl-c to quit while it is running. It
crashes (segfault) the interpreter every few times you stop it
Corey Goldberg added the comment:
yes if the new style was listed first, and the old style was below and
marked as "Old API", it would help with some confusion (like I ran into).
___
Python tracker
<http://bugs.python.
Corey Goldberg added the comment:
Just took another look. The doc is correct and already shows name and
daemon properties.
it was just confusing at first since where it says "Old API for name",
it links to the new style API and you jump to that section.
perhaps it could be s
Corey Goldberg added the comment:
sorry for the confusion. The doc might actually be correct, but it
seems ambiguous and confusing with respect to the name and daemon
properties.
if you look here:
http://docs.python.org/dev/py3k/library/threading.html
scroll down to where it says
New submission from Corey Goldberg :
In the current 3.0 doc for threading:
http://docs.python.org/dev/py3k/library/threading.htm
it says:
Thread.getName()
Thread.setName()
Old API for name.
and
Thread.isDaemon()
Thread.setDaemon()
Old API for daemon.
'name' a
