New submission from Xavier de Gaye:
Duplicate method names:
./Lib/xml/dom/minidom.py:379 Attr._get_name
--
components: Library (Lib)
messages: 198584
nosy: xdegaye
priority: normal
severity: normal
status: open
title: duplicate test name in Lib/xml/dom/minidom.py
type: behavior
versions
New submission from Xavier de Gaye:
Duplicate method names:
./Mac/Tools/Doc/setup.py:123 DocBuild.makeHelpIndex
--
components: Library (Lib)
messages: 198585
nosy: hynek, ned.deily, ronaldoussoren, xdegaye
priority: normal
severity: normal
status: open
title: duplicate test name in Mac
Xavier de Gaye added the comment:
The following issues have been entered for all the above duplicate
names found by duplicate_code_names_2.py:
issue 19112, issue 19113, issue 19114, issue 19115, issue 19116,
issue 19117, issue 19118, issue 19119, issue 19122, issue 19123,
issue 19125, issue
Xavier de Gaye added the comment:
After the last changeset 39f9adc8ad5b there are still 3 methods named
test_findleaks. The proposed patch was also missing one of them.
--
___
Python tracker
<http://bugs.python.org/issue19
Xavier de Gaye added the comment:
There is a backward compatibility issue with changeset d5ef330bac50
that enables tab-completion in the interactive interpreter by default.
When a user is not aware of this new feature and has been implementing
up to now her/his PYTHONSTARTUP file with the first
Xavier de Gaye added the comment:
The patch fixes the problem on my setup. A very minor glitch: after
manually emptying or removing the PYTHONSTARTUP history file, the
history is loaded with the content of ~/.python_history on the next
session
Xavier de Gaye added the comment:
It was proposed, in issue 16056, to enhance `make patchcheck` with the
detection of duplicate code names. This triggered the creation of issue 16079.
The script named duplicate_code_names_2.py, in issue 16079, listed about 20
duplicate names among all the non
Xavier de Gaye added the comment:
A less invasive alternative could be to instrument Bdb with a subclass
that processes send-expect sequences. This is what does
http://code.google.com/p/pdb-clone/source/browse/Lib/test/test_bdb.py
This code could be adapted to run with python bdb
Xavier de Gaye added the comment:
A description of what goes wrong when stepping out of the generator
would be helpful.
--
___
Python tracker
<http://bugs.python.org/issue16
Xavier de Gaye added the comment:
This is a consequence of the problem mentioned in msg 177059 above.
New patch 'issue16596_nostate_3.diff' fixes both problems by having the
interpreter
issue an exception debug event when processing a StopIteration in target
FOR_ITER:
* The same de
Xavier de Gaye added the comment:
Forgot to say that the only difference between this patch and the previous one
is in Python/ceval.c.
--
___
Python tracker
<http://bugs.python.org/issue16
Xavier de Gaye added the comment:
Hopefully issue16596_nostate_4.diff should fix this.
The patch issues a StopIteration debug event in ceval.c (similar to the change
made in the previous
patch for the for loop), when the subgenerator is exhausted. This debug event
is printed as
'Int
Xavier de Gaye added the comment:
> Sorry Xavier for your patches, but it's time to focus our efforts on a single
> module and asyncio has a much better design to handle such use cases.
No problem. Thanks for taking your time to review patches made on this
New submission from Jeroen de Jong:
I ma trying to find a way to round correctly. So far I get unexpected results
for some values.
--
components: Windows
files: Rounding.py
messages: 222444
nosy: jeroen1225
priority: normal
severity: normal
status: open
title: Rounding properly
type
Xavier de Gaye added the comment:
Python 3.5 is still crashing with this test:
$ python jump.py
> jump.py(7)()
-> for i in gen():
(Pdb) break 3
Breakpoint 1 at jump.py:3
(Pdb) continue
> jump.py(3)gen()
-> yield i
(Pdb) step
--Return--
> jump.py(3)gen()->0
-> yield i
(Pd
New submission from Xavier de Gaye:
The Py_XDECREF statement in gen_iternext() at Objects/genobject.c is not needed
since val is NULL (may be optimized out by the compiler).
Actually, the whole function could be written as:
return gen_send_ex(gen, NULL, 0);
--
components
Xavier de Gaye added the comment:
The previous patch changed a field in the PyThreadState structure. This new
patch is simpler and does not prevent to change f_lineno when it is not the
attribute of the frame being traced. The new patch fixes also issue 7238, issue
16482 and issue 17697
Xavier de Gaye added the comment:
Two issues here:
a) in IDLE, on a 'return' debug event in the main module, the step command does
not end the debugging session.
b) in IDLE, BdbQuit is raised by the quit command when the debugger is started
with pdb.set_trace().
I do not know I
Xavier de Gaye added the comment:
> # This returns to a '>>>' prompt,
At the above line in Terry test, the debugger is not terminated and on linux
when I type at this point I get:
>>>
--Call--
> /home/xavier/etc/.pystartup(21)save_history()
-> def save_h
New submission from Xavier de Gaye:
$ ./python
Python 2.7.8+ (2.7:5563f895b215, Jul 20 2014, 18:10:28)
[GCC 4.9.0 20140521 (prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import warnings
>>
Xavier de Gaye added the comment:
> The same kind of fix should also be applied to '_once_registry' and
> '_filters'.
Oops, no they are correctly refcounted.
--
___
Python tracker
<http
New submission from Vitor de Lima:
The atomic operations listed in the pyatomic.h header file were implemented
only for the x86 architecture, this patch uses the atomic bultins available in
GCC >= 4.7 to implement such operations, allowing it to work properly in other
platfo
Vitor de Lima added the comment:
Implemented a new version of the patch using either gcc builtins or the
stdatomic.h header (this is detected by the configure script).
--
Added file: http://bugs.python.org/file36151/atomicv2.patch
___
Python tracker
Xavier de Gaye added the comment:
This is because breakpoints number are class attributes. With the following
change, the "./python -m test test_pdb test_pdb" is ok:
$ hg diff
diff --git a/Lib/test/test_pdb.py b/Lib/test/test_pdb.py
--- a/Lib/test/test_pdb.py
+++ b/Lib/test/t
Xavier de Gaye added the comment:
Sorry, I posted to the wrong issue, please ignore my previous message.
--
___
Python tracker
<http://bugs.python.org/issue20
Changes by Xavier de Gaye :
Added file: http://bugs.python.org/file36163/refleak_3.patch
___
Python tracker
<http://bugs.python.org/issue20766>
___
___
Python-bugs-list m
Xavier de Gaye added the comment:
This is because breakpoints number are class attributes. With the following
change, the "./python -m test test_pdb test_pdb" is ok:
$ hg diff
diff --git a/Lib/test/test_pdb.py b/Lib/test/test_pdb.py
--- a/Lib/test/test_pdb.py
+++ b/Lib/test/t
Xavier de Gaye added the comment:
After refleak_3.patch, test_pdb_next_command_in_generator_for_loop is the only
remaining test that sets a breakpoint without reinitializing the breakpoints
numbering first.
As a result, this test may also fail in the future when tests are reordered by
the
New submission from Xavier de Gaye:
Pdb sets a handler for the SIGINT signal (which is sent when the user presses
Ctrl-C on the console) when you give a continue command.
'continue' is not the only pdb command that may be interrupted, all the
commands that resume the execution of t
Changes by Xavier de Gaye :
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue22135>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Xavier de Gaye:
When tracing, the frame of a suspended generator should not have an f_trace
function as there is no way to delete the frame f_trace attribute in that case
even though
tracing may have been disabled.
The patch relies on the fact that whenever the generator
New submission from Xavier de Gaye:
'test_faulthandler.patch' uses dedent to have triple-quoted strings in indented
form. This allows viewing the source code with the folding tools available with
some editors.
'test_faulthandler.diff' is the result of 'hg diff --igno
Changes by Xavier de Gaye :
Added file: http://bugs.python.org/file36322/test_faulthandler.diff
___
Python tracker
<http://bugs.python.org/issue22175>
___
___
Python-bug
Xavier de Gaye added the comment:
This issue can be closed.
After changeset 7bc53cf8b2df by Zachary Ware in issue 22104:
./python -m test -R3:3 test_statistics
is ok now.
--
nosy: +zach.ware
___
Python tracker
<http://bugs.python.org/issue20
New submission from Xavier de Gaye:
With the following script:
import time
def foo():
import pdb; pdb.set_trace()
while 1:
time.sleep(.5)
foo()
Hitting ^C after continue gives:
$ ./python foo.py
> foo.py(5)foo()
-> while 1:
(Pdb) continue
^C
Program interrupted. (Use
Xavier de Gaye added the comment:
This issue has been entered while checking for duplicate test names in issue
16079.
--
___
Python tracker
<http://bugs.python.org/issue19
New submission from Xavier de Gaye:
With the following pdb_jump.py script:
def foo(x):
import pdb; pdb.set_trace()
lineno = 3
lineno = 4
foo(1)
The change made to 'x' is lost after a jump to line 4:
$ ./python ~/tmp/test/pdb_jump.py
> ~/tmp/test/pdb_jump.py(3)foo()
Xavier de Gaye added the comment:
This seems to break BaseTestSuite.countTestCases when invoked after the
TestSuite has been run:
...
File "Lib/unittest/suite.py", line 42, in countTestCases
cases += test.countTestCases()
AttributeError: 'NoneType' obj
New submission from Xavier de Gaye:
The sys.settrace documentation states:
The trace function is invoked (with event set to 'call') whenever a new local
scope is entered;
it should return a reference to a local trace function to be used that scope,
or None if the scope shouldn’t
Changes by Xavier de Gaye :
--
keywords: +patch
Added file: http://bugs.python.org/file33246/f_trace.patch
___
Python tracker
<http://bugs.python.org/issue20
New submission from Xavier de Gaye:
Section 3.2 of 'The Python Language Reference' states:
f_trace, if not None, is a function called at the start of each source code
line
Run the attached tracer.py and see that although f_trace is None in both cases
when 'cmd' is eit
Xavier de Gaye added the comment:
A patch proposed in issue 20041 provides a backward compatible solution to this
performance enhancement.
--
___
Python tracker
<http://bugs.python.org/issue16
Xavier de Gaye added the comment:
A patch is proposed in issue 20041.
--
___
Python tracker
<http://bugs.python.org/issue20040>
___
___
Python-bugs-list mailin
Xavier de Gaye added the comment:
See also issue 20040.
--
nosy: +xdegaye
___
Python tracker
<http://bugs.python.org/issue11992>
___
___
Python-bugs-list mailin
Xavier de Gaye added the comment:
Adding the corresponding tests.
--
components: +2to3 (2.x to 3.x conversion tool) -Interpreter Core
Added file: http://bugs.python.org/file33260/tests.patch
___
Python tracker
<http://bugs.python.org/issue20
Changes by Xavier de Gaye :
--
components: +Interpreter Core -2to3 (2.x to 3.x conversion tool)
___
Python tracker
<http://bugs.python.org/issue20041>
___
___
Changes by Xavier de Gaye :
--
nosy: +xdegaye
___
Python tracker
<http://bugs.python.org/issue20061>
___
___
Python-bugs-list mailing list
Unsubscribe:
Laurent De Buyst added the comment:
The proposed patch does solve the infinite recursion bug, but a different
problem appears when resetting the same mock multiple times: it only works the
first time.
Using the patch as it stands:
>>> from unittest.mock import mock_open
>>&
Laurent De Buyst added the comment:
Sorry Michael, I should have read your second comment more closely since you
already pointed out that using a list as default argument is bad.
It is, however, easily fixed by changing to this:
def reset_mock(self, visited=None):
"Restore the mock o
Laurent De Buyst added the comment:
And here's an actual patch with the corrected code
--
Added file: http://bugs.python.org/file33463/issue18622_2.patch
___
Python tracker
<http://bugs.python.org/is
New submission from Xavier de Gaye:
With this script:
# START
def foo():
while 1:
pass
import pdb; pdb.set_trace()
foo()
# END
The following sequence of pdb commands aborts the script with a
KeyboardInterrupt exception:
next
Ctrl-C
continue
While the equivalent following
New submission from Xavier de Gaye:
The following code crashes python with:
python: Objects/object.c:512: PyObject_Str: Assertion `!PyErr_Occurred()'
failed.
on the tip of the default branch, but not on python 3.3.3.
import sys
error = None
try:
raise ValueError('some tex
New submission from Mauricio de Alencar:
The following code demonstrates an inconsistency of this method in dealing with
zeros after the decimal mark.
from decimal import Context
context = Context(prec=2)
for x in [100., 10., 1., 0.1]:
print(context.create_decimal_from_float(x
Mauricio de Alencar added the comment:
According to the docs (http://docs.python.org/3/library/decimal.html):
"The decimal module incorporates a notion of significant places so that 1.30 +
1.20 is 2.50. The trailing zero is kept to indicate significance. This is the
customary presentatio
Mauricio de Alencar added the comment:
I propose then to create a context setting that switches between the current
textual representation of a Decimal and one that is "right zeros padded" up to
context precision.
Such that the line:
print(Context(prec=4, precise
Mauricio de Alencar added the comment:
String formatting is completely unaware of the concept of *significant digits*.
The only format that can get it right for every case is the 'e'. But then you
always get the exponent, which is undesirable. I was hopeful that the decimal
mo
Mauricio de Alencar added the comment:
"Digits after the decimal mark" is not the same as "significant digits".
See https://en.wikipedia.org/wiki/Significant_figures
If I have a list of numbers [256.2, 1.3, 0.5] that have 3 significant digits
each, I would like to have them
Mauricio de Alencar added the comment:
> You need to stop lecturing.
I'm sorry, I didn't mean to offend anyone. I just felt I was failing to
communicate the issue when I got the suggestion to use format(Decimal(1),
".2f").
> The above sentence you wrote directly cont
Mauricio de Alencar added the comment:
Thank you. This function accomplishes what I need, avoiding the
float->string->Decimal conversion path.
I will use a slight variation of it accepting floats and a precision value:
from decimal import Decimal, Contextdef sigdec(f, prec):x =
C
New submission from Xavier de Gaye:
After an alarm handler raises an exception while a tracing function is being
invoked and when this exception is not caught by the tracing function, the
call_trampoline() function in sysmodule.c returns NULL and its caller,
trace_trampoline(), removes the
Xavier de Gaye added the comment:
The following code shows that the trace function is removed when an alarm
raises an exception and prints: 'trace function: None'
import sys, signal, time
def trace(frame, event, arg):
if frame.f_code.co_name == 'foo&#x
New submission from Xavier de Gaye:
The following line should be removed from test_ssl.py:
from unittest import mock
--
components: Library (Lib)
messages: 211148
nosy: xdegaye
priority: normal
severity: normal
status: open
title: test_ssl does not use mock
type: behavior
versions
Xavier de Gaye added the comment:
> A signal should not remove the trace function.
And a signal should be traced.
The attached patch postpones all signals except SIGINT while the trace function
is being invoked, and thus the signal is traced after returning from this
function.
My previ
Changes by Xavier de Gaye :
Added file: http://bugs.python.org/file34070/signal_test.py
___
Python tracker
<http://bugs.python.org/issue20601>
___
___
Python-bugs-list m
Xavier de Gaye added the comment:
With the previous patch, after the signal arrives and the first call to
PyErr_CheckSignals, PyErr_CheckSignals is called for each bytecode processed in
the eval loop
of the tracing function (and the eval loop of functions called by the tracing
function, and
Xavier de Gaye added the comment:
Hum hum, and now with this last patch PyErr_CheckSignals is called for each
traced line even when no signal is pending, which is worse than the previous
one as far as performance is concerned.
--
___
Python tracker
New submission from Xavier de Gaye:
Occurs on the tip of the Python default branch on ArchLinux when running 'make
html PYTHON=python2' from Doc/.
Traceback attached.
--
assignee: docs@python
components: Documentation
files: sphinx-err-DH3qAl.log
messages: 211311
nosy: d
Xavier de Gaye added the comment:
$ hg log -r tip
changeset: 89198:72f9b6222476
tag: tip
parent: 89195:dcbbff7e6b56
parent: 89197:f45d4823f63c
user:Ezio Melotti
date:Sat Feb 15 16:59:39 2014 +0200
summary: #19890: merge with 3.3.
The README.txt says:
A
New submission from Xavier de Gaye:
Issuing the 'continue' pdb command with a lazy_import.py script as:
# START of lazy_import.py
import sys, pdb
for m in sys.modules:
if m == 'sys':
pdb.set_trace()
# END of lazy_import.py
gives the following output:
$ p
New submission from Xavier de Gaye:
After the pdb 'continue' command, the signal module owns a reference to
Pdb.sigint_handler. On the next instantiation of pdb, the signal module owns a
reference to a new sigint_handler method that owns a reference to the previous
sigint_han
Xavier de Gaye added the comment:
> the first pdb instance is never freed
The first pdb instance is (and all the other pdb instances) never freed until
the call to PyOS_FiniInterrupts() in Py_Finalize().
--
___
Python tracker
&l
Xavier de Gaye added the comment:
The doctests are executed with 'test.globs' as globals which is set in the
'find' method of doctest.DocTestFinder, and cleared after each run (unless
'clear_globs' is false). One possible fix is to have test.regrtest 'find&
Xavier de Gaye added the comment:
After applying patch 'regrtest.diff' from issue 20746, the command:
$ ./python -m test -W -R3:3 test_pdb
succeeds now and shows there are no reference leaks.
However, with the following change in Lib/test/test_pdb.py and patch
'regrtes
Xavier de Gaye added the comment:
See also issue 20766.
--
___
Python tracker
<http://bugs.python.org/issue20746>
___
___
Python-bugs-list mailing list
Unsub
Xavier de Gaye added the comment:
Documentation update attached.
--
Added file: http://bugs.python.org/file34326/pdb_doc.diff
___
Python tracker
<http://bugs.python.org/issue16
New submission from samuel de framond :
consider a program like this one:
File: ./test.py
#/usr/bin/env python
#coding: utf8
print 'qwerty'
-
Here is a shell (e.g. bash) session:
$ python -m pdb ./test.py
--Return--
> /usr/lib/python2.6/encoding
Gaëtan de Menten added the comment:
Regarding the issue J. David Ibáñez has, I have a few comments to add:
- It's also present on 32bit.
- AFAICT:
* it's present in both 2.6 branch & trunk (as of 68886),
* it's a problem with line 1110 (in 2.6 branch), or line 1122 in
New submission from Vito De Tullio :
RawConfigParser does not inherit from object, so using (to make an
example) super() it's impossible.
Python 2.6 (r26:66714, Feb 3 2009, 20:52:03)
[GCC 4.3.2 [gcc-4_3-branch revision 141291]] on linux2
Type "help", "copyright", &
New submission from Niels de Vos :
The last example of traceback (found on
<http://docs.python.org/library/traceback.html> release 2.6.2) contains
a typo.
>>> theError = IndexError('tuple indx out of range')
>>> traceback.format_exception_only(type(theError
New submission from Vito De Tullio :
from http://docs.python.org/download.html and
http://docs.python.org/3.0/download.html you can download the python
documentation in many formats (html, pdf, txt), I think auto-generated
by the .rst source.
While html and txt does not, the pdf format
Gabriel de Perthuis added the comment:
Apparently the pool workers die all at once, just after the pool creates
them and before the pool is used.
I added a few lines to multiprocessing/pool.py to get the stack and the
exception backtrace.
except (EOFError, IOError):
import
New submission from Michiel de Hoon :
(The discussion for this bug started on the pythonmac-sig mailing list; see
http://mail.python.org/pipermail/pythonmac-sig/2010-May/022362.html)
When I try to install Python as a framework:
./configure --enable-framework
make
make install
then Python
Michiel de Hoon added the comment:
The patch fixes the problem on Mac OS X 10.4. I'll try on 10.5 tomorrow.
Thanks!
--
___
Python tracker
<http://bugs.python.org/i
Michiel de Hoon added the comment:
The patch solves the problem also on Mac OS X 10.5 (I tried 32-bits and 64-bits
with the current python in trunk, after applying the patch).
Thanks again!
--
___
Python tracker
<http://bugs.python.org/issue8
Changes by Palluat de Besset :
--
assignee: ronaldoussoren
components: Macintosh
nosy: mpalluat, ronaldoussoren
priority: normal
severity: normal
status: open
title: subprocess module causing crash
type: crash
versions: Python 3.1
___
Python tracker
New submission from Palluat de Besset :
there is a crash log inside the archive
--
Added file: http://bugs.python.org/file17898/OSDP2.zip
___
Python tracker
<http://bugs.python.org/issue9
Palluat de Besset added the comment:
Hi Ronald,
Thank you for looking into it, and sorry for the misleading title.
You will find a crash log and some instructions on how to reproduce the problem
inside the archive.
Thanks,
Marc
On 8 Jul 2010, at 10:18, Ronald Oussoren wrote:
Ronald
New submission from Xavier de Gaye :
Python 2.7 - svn revision 82852
Bug description
===
Test script foo.py
--
#!/usr/bin/env python
import distutils.core
import test.regrtest
Exception when running foo.py
-
Traceback
Xavier de Gaye added the comment:
http://pyclewn.sourceforge.net uses the regrtest module to run its
testsuite.
The test package is documented in the Standard Library documentation,
quote:
"The test package contains all regression tests for Python as well
as the modules test.test_suppor
Xavier de Gaye added the comment:
Thanks for your comments, that was fast!
I will skip using the test package then.
--
status: pending -> open
___
Python tracker
<http://bugs.python.org/iss
Changes by Xavier de Gaye :
--
status: open -> pending
___
Python tracker
<http://bugs.python.org/issue9250>
___
___
Python-bugs-list mailing list
Unsubscri
New submission from Roald de Vries :
Exception raised::
Traceback (most recent call last):
File "bug.py", line 5, in
class derived(type, Sized):
File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/abc.py",
line 85, in __new
New submission from Valeo de Vries :
I'm under the impression that this is issue is known about, however I couldn't
find an existing bug, so I'm creating a new one for the following test failure:
test_distutils
/usr/lib/gcc/i686-pc-linux-gnu/4.4.4/../../../../i686-pc-linux-gnu/
Valeo de Vries added the comment:
Thanks for the speedy response! I'm fairly certain that this affects 2.6.5 as
well. I'll test and report back when I'm in front of my development machine
(sometime tomorrow).
--
___
Python
Irmen de Jong added the comment:
Due to lack of example code to reproduce the issue, and because I'm mildly
interested in this bug because it mentions Pyro4 (because I'm the author of
that) I've tried to crash my system myself using Pyro4 and a simple torture
test but it truck
Irmen de Jong added the comment:
The 28673-reproduce.py didn't crash on any of the systems I've tried it on. Are
you sure it is complete? It looks like a part is missing.
--
___
Python tracker
<http://bugs.python.o
New submission from Xavier de Gaye:
With this patch, cross compiling a third-party extension module is done with
the command:
XBUILD_PYTHON_DIR=/path/to/python/dir python setup.py build
where XBUILD_PYTHON_DIR is the location of the directory of the cross-compiled
python executable.
It may
Xavier de Gaye added the comment:
> This approach will not work with a "multiarch" enabled environment, and break
> cross builds on Debian and Ubuntu.
No, the patch does not break cross builds on Debian and Ubuntu, unless you can
demonstrate it does.
> Afaics, the propos
Changes by Xavier de Gaye :
--
nosy: +Chi Hsuan Yen
___
Python tracker
<http://bugs.python.org/issue28833>
___
___
Python-bugs-list mailing list
Unsubscribe:
Xavier de Gaye added the comment:
> I don't think that identifying the target by some path is the right way to
> go, and you should be able to identify the target by giving the target
> triplet as used by the configure parameters and then deduce the location from
> the t
801 - 900 of 1792 matches
Mail list logo
