New submission from Paul Melis:
The current 2.5 documentation does not seem to describe the OptionGroup
feature of the optparse module.
In 2003 there was a patch submitted that added a section on OptionGroup (
http://bugs.python.org/issue697941). The issue entry mentions it was
accepted, but
Paul Melis added the comment:
It seems it got edited out when the documentation was overhauled for
optik 1.5, in r37468
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Paul Melis added the comment:
Here's a patch that removes the
pysqlite_do_all_statements(self, ACTION_RESET, 0);
call.
It also adds the sqlite error code to one of the exceptions raised, as the
error message is misleading in case the ACTION_RESET is left in (I forgot what
sqlite err
Paul Melis added the comment:
Just a bit more info on the patch. When running stock Python 2.7.4 the attached
test script bug-binding_parameter_0.py returns:
module: 2.6.0
sqlite: 3.7.9
Archives
Archives/2011
Archives/2012
Traceback (most recent call last):
File "bug-binding_parameter
New submission from Paul Melis <[EMAIL PROTECTED]>:
On the 3.0 release page (http://python.org/download/releases/3.0/) the
link to the online documentation is http://docs.python.org/dev/3.0.
However, the doc pages there show the version documented to be "Python
v3.1a0". The
New submission from Paul Melis <[EMAIL PROTECTED]>:
The second to last item under "Removed Syntax" (about relative imports)
shows ReST markup in the HTML file, probably not the way it should read:
The only acceptable syntax for relative imports is from .``[*module*]
:keywor
Paul Melis added the comment:
The "archive" and "subscribe" links for the C++ SIG is incorrect, as the
URL seems to have changed from
http://mail.python.org/pipermail/c++-sig
to
http://mail.python.org/pipermail/cplusplus-sig
---
Paul Melis <[EMAIL PROTECTED]> added the comment:
I think I'm having a similar lockup on fedora core 4 (smp machine). This
is with the py3k branch, freshly svn updated. When running "make test
TESTOPTS=test_multiprocessing" the first of the two test runs always
succeeds in
Paul Melis <[EMAIL PROTECTED]> added the comment:
After a few more runs with -v and redirecting output to a file it seems
the lockup I get is in
test_notify_all (test.test_multiprocessing.WithManagerTestCondition)
___
Python tracker <[EMAIL PROTECTE
Paul Melis <[EMAIL PROTECTED]> added the comment:
I made a copy of test_multiprocessing.py (to test_mp.py) and basically
removed all test classes, except _TestCondition. In it, I commented all
test methods except test_notify_all. When run with make test
TESTOPTS="-v test_mp" the
Paul Melis <[EMAIL PROTECTED]> added the comment:
What do you mean with ">16MB"? Is that the total size of all data held
by the dictionary (and if so, how did you measure this)? How many keys
are in the dictionary? And what indication do you have that elements are
being droppe
Paul Melis <[EMAIL PROTECTED]> added the comment:
The script is still not a test case, as it doesn't *demonstrate* the
problem when run. You need to provide more information for this to be
reproducable by others.
- what exact input did you use? (e.g. include the IRC log file on whic
Paul Melis <[EMAIL PROTECTED]> added the comment:
On a Linux system (FC4) with r64686 of the Py3k branch I also still get
occassional hangs (with ./python -E -bb ./Lib/test/regrtest.py -v
test_multiprocessing). Mostly this seems to occur with the very first
test executed, i.e. before any
13 matches
Mail list logo
