Duncan Findlay dun...@duncf.ca added the comment:
I've been digging into this quite a bit, and I've been able to dig up a little
more info.
* In Python 2.1, the behavior was very similar to what we have now -- signals
were not blocked. http://bugs.python.org/issue465673 was filed reporting
Duncan Findlay dun...@duncf.ca added the comment:
This is definitely still an issue.
With the pthread_sig patch attached to this bug, both on FreeBSD and on
linux, any processes spawned from a thread seem to have their signals blocked,
so they can not be killed.
Without it, on FreeBSD
Changes by Duncan Findlay dun...@duncf.ca:
Removed file: http://bugs.python.org/file20046/thread_test.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1975
Changes by Duncan Findlay dun...@duncf.ca:
Added file: http://bugs.python.org/file20047/thread_test.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1975
Changes by Duncan Findlay dun...@duncf.ca:
--
nosy: +duncf
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1975
___
___
Python-bugs-list mailing
Changes by Duncan Findlay dun...@duncf.ca:
--
nosy: +duncf
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10470
___
___
Python-bugs-list mailing
New submission from Duncan Findlay du...@apache.org:
According to the documentation for tokenize.generate_tokens:
The generator produces 5-tuples with these members: the token type; the
token string; a 2-tuple (srow, scol) of ints specifying the row and
column where the token begins
