New submission from Mark Summerfield [EMAIL PROTECTED]:
The 30a4 RELNOTES file doesn't cover 30a3 or 30a4.
--
assignee: georg.brandl
components: Documentation
messages: 64918
nosy: georg.brandl, mark
severity: normal
status: open
title: Py30a4 RELNOTES only cover 30a1 and 30a2
type:
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Without a single hint about the code your are running, no investigation
is possible. And since the traceback shows that the python interpreter
is embedded in another application, it could very well be an error in
your C code.
Please
New submission from Thomas Heller [EMAIL PROTECTED]:
[Found by Daniel Diniz (ajaksu2), see issue #2542]
The following code triggers an undetected error with a debug build:
import sys
def g():
try:
return g()
except:
return sys.exc_info()
g()
print 42
Running the code prints
Thomas Heller [EMAIL PROTECTED] added the comment:
Daniel, IMO you've found a separate bug. I added it as issue #2548.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2542
__
Thomas Heller [EMAIL PROTECTED] added the comment:
Committed as rev 62143.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2543
__
Thomas Heller [EMAIL PROTECTED] added the comment:
Committed as rev 62145.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2544
__
Fred L. Drake, Jr. [EMAIL PROTECTED] added the comment:
Of course, my previous commit did what I said it should not in #1 above:
it changed the current directory to the directory in which the setup.py
script lived (which made __file__ wrong).
Fixed in revision 62147, including test that checks
Tarek Ziadé [EMAIL PROTECTED] added the comment:
right, I misused os.curdir, I wanted the current working directory.
(getcwd())
Thanks for correcting it and making it a separate patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2385
Fred L. Drake, Jr. [EMAIL PROTECTED] added the comment:
Updated patch to add restoring the current directory after running the
setup.py script in run_script.
Added file: http://bugs.python.org/file9937/run_script-restores-cwd.patch
__
Tracker [EMAIL PROTECTED]
Changes by Fred L. Drake, Jr. [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file9936/run_script-restores-cwd.patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2385
__
Fred L. Drake, Jr. [EMAIL PROTECTED] added the comment:
It's also arguable that not providing __file__ was a bug, in which case
that should be backported to Python 2.5.x.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2385
Guilherme Polo [EMAIL PROTECTED] added the comment:
While we are at it, can't we revamp nametowidget too ?
Patch attached
--
nosy: +gpolo
Added file: http://bugs.python.org/file9938/bugfix_and_revamp_nametowidget.diff
Tracker [EMAIL PROTECTED]
Changes by jan matejek [EMAIL PROTECTED]:
--
nosy: +matejcik
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1179
__
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Chabod [EMAIL PROTECTED]:
shutil generate a NameError (WindowsError) exception when moving a
directory from an ext3 to a fat32 under linux
To reproduce it:
under linux, current path on an ext3 filesytem, try to enter following
commands:
mkdir toto #on an ext3 partition
Changes by Chabod [EMAIL PROTECTED]:
--
title: shutil: NameError (WindowsWrror) when moving from ext3 to fat32 under
linux - shutil: NameError (WindowsError) when moving from ext3 to fat32 under
linux
__
Tracker [EMAIL PROTECTED]
Changes by Trent Nelson [EMAIL PROTECTED]:
--
assignee: - Trent.Nelson
keywords: +easy
nosy: +Trent.Nelson
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2549
__
___
Raghuram Devarakonda [EMAIL PROTECTED] added the comment:
This problem has been noticed as part of issue1545 and a patch with the
fix has been proposed but has a small problem with it. Do you want to
take a look?
--
nosy: +draghuram
__
Tracker [EMAIL
Alexander Belopolsky [EMAIL PROTECTED] added the comment:
On Thu, Apr 3, 2008 at 9:39 PM, Raymond Hettinger
[EMAIL PROTECTED] wrote:
It's definitely a bug
What would you say to the following:
def f(x):
pass
class X:
xf = f
x = X()
x.xf(1,2)
-- TypeError: f() takes exactly 1
New submission from Trent Nelson [EMAIL PROTECTED]:
Background: I came across this issue when trying to track down why
test_asynchat would periodically wedge python processes on the Windows
buildbots, to the point that they wouldn't even respond to SIGKILL (or
ctrl-c on the console).
What I
Mark Dickinson [EMAIL PROTECTED] added the comment:
I'm almost tempted to call the first of these a bug: isn't '((x|y)*)*'
a perfectly valid (albeit somewhat redundant) regular expression? What
am I missing here?
Even if there are issues with capturing, shouldn't the version without
capturing
Changes by Trent Nelson [EMAIL PROTECTED]:
--
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2296
__
___
Python-bugs-list mailing list
Kurt B. Kaiser [EMAIL PROTECTED] added the comment:
I don't think that this is an IDLE error. It
can be more generally exhibited as follows:
Without the subprocess we get the expected:
IDLE 3.0a4 No Subprocess
eval('a')
Traceback (most recent call last):
File pyshell#0,
Lorenz Quack [EMAIL PROTECTED] added the comment:
I confirmed that the rlcompleter can raise a SyntaxError on bad input.
Upon further investigation I found that a ReferenceError could also be
raised. I didn't check on other Exceptions.
I attached a new version of the patch where I catch all
New submission from Jean Brouwers [EMAIL PROTECTED]:
Below is the tail of the output of 'make test' for 32-bit Python 2.6a2
on Solaris 10 (Opteron) built with the SUN C compiler.
310 tests OK.
1 test failed:
test_ioctl
41 tests skipped:
test_aepack test_al test_applesingle test_bsddb
Thomas Heller [EMAIL PROTECTED] added the comment:
On *nix-like systems, ctypes will most likely only compile with gcc.
Since I do not have access to such systems, neither the expertise for
them, this will not change unless someone provides patches.
--
nosy: +theller
Robert Schuppenies [EMAIL PROTECTED] added the comment:
I can *not* confirm the leak. I tested using the provided scripts (with
little modifications to log memory usage), using 1000 instead of 20
runs. I am running on Debian Linux and checked the reported Python
2.4.2 and the current trunk
Changes by Robert Schuppenies [EMAIL PROTECTED]:
Added file: http://bugs.python.org/file9942/memory2.6a2.csv
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1517495
_
___
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Please create one report per issue.
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2551
__
___
New submission from Jean Brouwers [EMAIL PROTECTED]:
The ctypes test failed since the _ctypes module did not compile for 32-
bit Python 2.6a2 on Solaris 10 (Opteron) built with the SUN C compiler.
...
cc -KPIC -xtarget=native -DNDEBUG -xO5 -I. -I/.../tools/Python-
2.6a2/./Include
New submission from Jean Brouwers [EMAIL PROTECTED]:
The test_ioctl failed in 32-bit Python 2.6a2 built on Solaris 10 with
the SUNC C compiler.
...
test test_ioctl failed -- Traceback (most recent call last):
File /.../tools/Python-2.6a2/Lib/test/test_ioctl.py, line 56, in
New submission from Jean Brouwers [EMAIL PROTECTED]:
For 32-bit Python 2.6a2 on Solaris 10 (Opteron) built with the SUN C
compiler this test_parser failure does not show up in the summary.
...
test_parser
Expecting 's_push: parser stack overflow' in next line
s_push: parser stack overflow
...
Jean Brouwers [EMAIL PROTECTED] added the comment:
This is a duplicate. Please ignore. My apologies.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2553
__
___
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Are you interested in working on a patch?
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2552
__
Jean Brouwers [EMAIL PROTECTED] added the comment:
Done, see issues 2552, 2554 and 2555. Please ignore, close duplicate
2553.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2551
__
Guilherme Polo [EMAIL PROTECTED] added the comment:
This still happens, but around 2000 iterations here on newer Python
versions (trunk, 3alpha, 2.5.x, 2.4.x). Using Python 1.6 I've got it at
2 iterations (min), but.. is this going to be fixed or given the amount
of iterations needed nowadays
New submission from Jean Brouwers [EMAIL PROTECTED]:
The test_ioctl failed in Python 2.6a2 built on Solaris 10 with the SUNC
C compiler.
...
test test_ioctl failed -- Traceback (most recent call last):
File /.../tools/Python-2.6a2/Lib/test/test_ioctl.py, line 56, in
Jason Orendorff [EMAIL PROTECTED] added the comment:
Huh. Maybe you're right. JavaScript, Ruby, and Perl all accept both
regexes, although no two agree on what should be captured:
js xyyzy.replace(/((x|y)*)*/, ($1, $2))
(xyy, y)zy
js xyyzy.replace(/((x|y+)*)*/, ($1, $2))
(xyy, yy)zy
Guilherme Polo [EMAIL PROTECTED] added the comment:
Indeed, it should call self._getints, not sure why it was never done.
Fixing this gives curselection the correct behavior according to the Tk
Reference Manual: http://tmml.sourceforge.net/doc/tk/listbox.html
--
nosy: +gpolo
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
The problem is just that in Python/pythonrun.c, the function run_mod()
calls flush_io() after executing the code. In our testcase, there is a
pending exception.
But flush_io() silently ignore errors (which is fine), and clears all
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Committed r62157.
Will also investigate why exec() needs to flush sys.stdout...
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2221
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Analysis: the primary recursion error is correctly raised, but then
there is a call to PyErr_NormalizeException, which calls
PyEval_CallObject, which increases the stack depth and hit the recursion
limit again...
python2.5 don't have the
Neal Norwitz [EMAIL PROTECTED] added the comment:
I think this was a module that I skipped. I think Anthony might have
had a patch, but if we have a fix, I'm not sure it matters. We need to
fix this for 2.5.3, upping the priority.
--
nosy: +anthonybaxter
priority: high - release
Kurt B. Kaiser [EMAIL PROTECTED] added the comment:
Thanks, that does appear to fix the IDLE problem!
The pseudofile does have a flush method and I was able to
call it from the IDLE subprocess; it returns None. So I'm
not clear on why PyObject_CallMethod was returning False, or
why the
Terry J. Reedy [EMAIL PROTECTED] added the comment:
While I agree with Raymond that the interpreter should be left alone,
this could be reclassified (and reopened) as a doc issue. The current
trace doc (Lib Ref 25.10) says rather tersely The trace module allows
you to trace program execution,
Neal Norwitz [EMAIL PROTECTED] added the comment:
Gerhard, could you take a look?
--
assignee: - ghaering
nosy: +ghaering, nnorwitz
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2515
__
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
priority: - release blocker
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2515
__
___
Python-bugs-list mailing list
Neal Norwitz [EMAIL PROTECTED] added the comment:
Eric, could you take a look?
--
assignee: - eric.smith
nosy: +eric.smith, nnorwitz
priority: - high
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2526
__
Neal Norwitz [EMAIL PROTECTED] added the comment:
I'm setting the priority to release blocker for now. George, please
provide a way for us to reproduce with a stock python (ie, no third
party extensions). Thanks.
--
nosy: +nnorwitz
priority: - release blocker
Neal Norwitz [EMAIL PROTECTED] added the comment:
Brett, didn't you have a similar problem you fixed a while ago? I
assigned to you for more input, feel free to reset to nobody.
--
assignee: - brett.cannon
nosy: +brett.cannon, nnorwitz
priority: - release blocker
Changes by Daniel Diniz [EMAIL PROTECTED]:
--
nosy: +ajaksu2
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2548
__
___
Python-bugs-list mailing list
Unsubscribe:
Martin v. Löwis [EMAIL PROTECTED] added the comment:
This is not a bug. How should we phrase the first line to make that
unobviously clear?
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2555
__
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Thanks!
--
resolution: - duplicate
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2551
__
Changes by Martin v. Löwis [EMAIL PROTECTED]:
--
resolution: - duplicate
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2553
__
___
Neal Norwitz [EMAIL PROTECTED] added the comment:
Travis, could you take a look?
--
assignee: - teoliphant
nosy: +nnorwitz, teoliphant
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2538
__
54 matches
Mail list logo