[issue1296] optparse's OptionGroup not described

2007-10-18 Thread Paul Melis

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 the current docs do not seem to contain that section.

--
components: Documentation
messages: 56526
nosy: paulmelis
severity: normal
status: open
title: optparse's OptionGroup not described
versions: Python 2.5

__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1296>
__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue1296] optparse's OptionGroup not described

2007-10-18 Thread Paul Melis

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/issue1296>
__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue3088] test_multiprocessing hangs on OS X 10.5.3

2008-06-12 Thread Paul Melis

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 something like 10-15 seconds, while the second one
occasionally hangs. I tried running with -v as extra argument but can't
get it to hang in that case (to figure out which test is the culprit).

--
nosy: +paulmelis

___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3088>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue3088] test_multiprocessing hangs on OS X 10.5.3

2008-06-12 Thread Paul Melis

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 PROTECTED]>
<http://bugs.python.org/issue3088>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue3088] test_multiprocessing hangs on OS X 10.5.3

2008-06-13 Thread Paul Melis

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" there's the lockups every few runs, but I also got
(only three times in 40 or so runs so far):


9:57|[EMAIL PROTECTED]:~/c/py3k-svn> make test TESTOPTS="-v test_mp"

Failed to find the necessary bits to build these modules:
_gestalt
To find the necessary bits, look in setup.py in detect_modules() for the
module's name.

find ./Lib -name '*.py[co]' -print | xargs rm -f
./python -E -bb ./Lib/test/regrtest.py -v test_mp
test_mp
test_notify_all (test.test_mp.WithProcessesTestCondition) ... ok
test_notify_all (test.test_mp.WithThreadsTestCondition) ... ok
test_notify_all (test.test_mp.WithManagerTestCondition) ... ok

--
Ran 3 tests in 1.087s

OK
1 test OK.
CAUTION:  stdout isn't compared in verbose mode:
a test that passes in verbose mode may fail without it.
./python -E -bb ./Lib/test/regrtest.py -v test_mp
test_mp
test_notify_all (test.test_mp.WithProcessesTestCondition) ... ok
test_notify_all (test.test_mp.WithThreadsTestCondition) ... ok
test_notify_all (test.test_mp.WithManagerTestCondition) ... Exception in
thread Thread-28:
Traceback (most recent call last):
  File "/home/paul/c/py3k-svn/Lib/threading.py", line 492, in
_bootstrap_inner
self.run()
  File "/home/paul/c/py3k-svn/Lib/threading.py", line 447, in run
self._target(*self._args, **self._kwargs)
  File "/home/paul/c/py3k-svn/Lib/test/test_mp.py", line 208, in f
cond.wait(timeout)
  File "/home/paul/c/py3k-svn/Lib/multiprocessing/managers.py", line
973, in wait
return self._callmethod('wait', (timeout,))
  File "/home/paul/c/py3k-svn/Lib/multiprocessing/managers.py", line
748, in _callmethod
raise convert_to_error(kind, result)
RuntimeError: cannot wait on un-aquired lock

___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3088>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue3104] overzealous garbage collector (dict)

2008-06-13 Thread Paul Melis

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 dropped?

--
nosy: +paulmelis

___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3104>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue3104] overzealous garbage collector (dict)

2008-06-14 Thread Paul Melis

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 which
you claim a bug is exposed)
- what output/behaviour did you expect for the given input?
- how was the actual output/behaviour different from what was expected?

___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3104>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue3088] test_multiprocessing hangs on OS X 10.5.3

2008-07-03 Thread Paul Melis

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 of the "test_... " lines have been generated.

The following may or may not be related. Some time ago I decided to give
valgrind a try to see if it could detect anything strange going on with
the multiprocessing tests, specifically using the 'helgrind'
thread-debugging tool that comes with it. 

Valgrind reports as its first error:

==9719== Thread #1: Bug in libpthread: sem_wait succeeded on semaphore
without prior sem_post
==9719==at 0x4007FFF: sem_wait_WRK (hg_intercepts.c:1057)
==9719==by 0x4008094: [EMAIL PROTECTED] (hg_intercepts.c:1073)
==9719==by 0x46A0087: semlock_acquire (semaphore.c:310)
==9719==by 0x808C121: PyEval_EvalFrameEx (ceval.c:3371)
==9719==by 0x808D0FE: PyEval_EvalCodeEx (ceval.c:2808)
==9719==by 0x808B9D0: PyEval_EvalFrameEx (ceval.c:3469)
==9719==by 0x808D0FE: PyEval_EvalCodeEx (ceval.c:2808)
==9719==by 0x80F4B65: function_call (funcobject.c:628)
==9719==by 0x80D1207: PyObject_Call (abstract.c:2178)
==9719==by 0x80890EC: PyEval_EvalFrameEx (ceval.c:3672)
==9719==by 0x808C1A9: PyEval_EvalFrameEx (ceval.c:3459)
==9719==by 0x808C1A9: PyEval_EvalFrameEx (ceval.c:3459)
==9716== Thread #1 is the program's root thread

I've been hesitant to report this as the claim that libpthread is broken
is pretty bold. I contacted the valgrind devs about this, see [1]. 
More recently, someone on the valgrind list reported problems that do
seem to indicate there are broken libpthreads out there (see [2]), as
this individual reports a semaphore wait not blocking where it should.

Could it be that the multiprocessing tests are exposing one or more bugs
in libpthread?

[1] http://thread.gmane.org/gmane.comp.debugging.valgrind/8345
[2] http://thread.gmane.org/gmane.comp.debugging.valgrind/8384

___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3088>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue4520] Online 3.0 documentation says it's for 3.1a0

2008-12-04 Thread Paul Melis

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". There's even a link called "What's new in Python 3.1?" that
doesn't work.

Could it be that the pages currently under
http://docs.python.org/dev/3.0 should have gone under
http://docs.python.org/dev/3.1?

--
assignee: georg.brandl
components: Documentation
messages: 76876
nosy: georg.brandl, paulmelis
severity: normal
status: open
title: Online 3.0 documentation says it's for 3.1a0
versions: Python 3.0, Python 3.1

___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4520>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue4546] Small thingy in "What's New in Python 3.0"

2008-12-05 Thread Paul Melis

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*]
:keyword:`import` *name*; :keyword:`import` forms not starting with ``.
are always interpreted as absolute imports.

--
assignee: georg.brandl
components: Documentation
messages: 77010
nosy: georg.brandl, paulmelis
severity: normal
status: open
title: Small thingy in "What's New in Python 3.0"
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4546>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue4137] update SIG web pages

2009-02-05 Thread Paul Melis

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

--
nosy: +paulmelis

___
Python tracker 
<http://bugs.python.org/issue4137>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10513] sqlite3.InterfaceError after commit

2013-04-22 Thread Paul Melis

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 error is actually raised in that case).

I've been using this patch for some while now with 2.7.3 and it fixes similar 
problems as noted in this thread.

--
keywords: +patch
nosy: +paulmelis
Added file: http://bugs.python.org/file29981/bug10513.patch

___
Python tracker 
<http://bugs.python.org/issue10513>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10513] sqlite3.InterfaceError after commit

2013-05-01 Thread Paul Melis

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_0.py", line 45, in 
cur = dbconn.execute('select uidvalidity from folders where name=?', 
(folder,))
sqlite3.InterfaceError: Error binding parameter 0 - probably unsupported type.

The error suggests a misuse of the sqlite3 API, but the actual SQLite error is 
masked. After altering _sqlite/statement.c to include the SQLite error code (as 
in the patch), we get:

module: 2.6.0
sqlite: 3.7.9
Archives
Archives/2011
Archives/2012
Traceback (most recent call last):
  File "bug-binding_parameter_0.py", line 45, in 
cur = dbconn.execute('select uidvalidity from folders where name=?', 
(folder,))
sqlite3.InterfaceError: Error binding parameter 0 - probably unsupported type. 
(sqlite error 21)

Error 21 = SQLITE_MISUSE, suggesting something is definitely wrong in the way 
the SQLite API is used (for this test case). Commenting out the ACTION_RESET 
all works fine again:

module: 2.6.0
sqlite: 3.7.9
Archives
Archives/2011
Archives/2012

--
Added file: http://bugs.python.org/file30087/bug-binding_parameter_0.py

___
Python tracker 
<http://bugs.python.org/issue10513>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com