The threading module contains buggy code:
assert self.__initialized, "Thread.__init__() not called"
assert not self.__started, "thread already started"
If you run such code with python -O, weird stuff may happen when you
call mythread.start() multiple times. -O removes assert statements so
the code won't fail with an AssertionError which would be expected.
So what real exception should Thread.start() raise? I have suggested
adding an IllegalStateError modelled after java's
IllegalStateException, but that idea was rejected. So what exception
should be raised here, is it a RuntimeError?
I've rewritten large portions of PEP 3101, incorporating some material
from Patrick Maupin and Eric Smith, as well as rethinking the whole
custom formatter design. Although it isn't showing up on the web site
yet, you can view the copy in subversion (and the diffs) here:
Please let me know of any errors you find, either by mailing me
directly, or replying to the topic in Python-3000. (I.e. lets not start
a thread here.)
ACTIVITY SUMMARY (05/27/07 - 06/03/07)
Tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
1649 open ( +0) / 8584 closed ( +0) / 10233 total ( +0)
Average duration of open issues: 813 days.
Median duration of open issues: 764 days.
Open Issues Breakdown
open 1649 ( +0)
pending 0 ( +0)
I have been getting failures from test_sqlite off the trunk when I run the
entire test suite (as ``./python.exe Lib/test/regrtest.py``) with this error
on OS X 10.4.9 and sqlite3 3.3.16:
Traceback (most recent call last):
29, in setUp
self.con = sqlite.connect(":memory:")
ProgrammingError: library routine called out of sequence
When run in isolation it is fine. Anyone have a guess as to what is going