[issue2547] Py30a4 RELNOTES only cover 30a1 and 30a2
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: feature request versions: Python 3.0 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2547 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2546] Python-2.5.2: crash in visit_decref () at Modules/gcmodule.c:270
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 provide a way to reproduce the problem. -- nosy: +amaury.forgeotdarc __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2546 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2548] Undetected error in exception handling
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 this: C:\svn\trunk\PCbuildpython_d test2.py 42 XXX undetected error Traceback (most recent call last): File test2.py, line 8, in module print 42 RuntimeError: maximum recursion depth exceeded [8826 refs] C:\svn\trunk\PCbuild -- components: Interpreter Core messages: 64920 nosy: theller severity: normal status: open title: Undetected error in exception handling type: crash versions: Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2548 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2542] PyErr_ExceptionMatches must not fail
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2543] Make ctypes compatible with Python 2.3, 2.4, and 2.5, as per PEP291
Thomas Heller [EMAIL PROTECTED] added the comment: Committed as rev 62143. -- resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2543 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2544] link with gcc -shared on HP systems
Thomas Heller [EMAIL PROTECTED] added the comment: Committed as rev 62145. -- resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2544 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2385] run_setup can fail if the setup script uses __file__
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 that the script is run in the current directory of the caller. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2385 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2385] run_setup can fail if the setup script uses __file__
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2385] run_setup can fail if the setup script uses __file__
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] http://bugs.python.org/issue2385 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2385] run_setup can fail if the setup script uses __file__
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2385] run_setup can fail if the setup script uses __file__
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue799428] tk_focusNext() fails
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] http://bugs.python.org/issue799428 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1179] [CVE-2007-4965] Integer overflow in imageop module
Changes by jan matejek [EMAIL PROTECTED]: -- nosy: +matejcik __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1179 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2549] shutil: NameError (WindowsWrror) when moving from ext3 to fat32 under linux
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 python import shutil shutil.move(toto, /media/fat32/toto) # /media/fat32 is mounted on a fat32 filesystem You will produce following error: Traceback (most recent call last): File stdin, line 1, in module File /usr/lib/python2.5/shutil.py, line 196, in move copytree(src, dst, symlinks=True) File /usr/lib/python2.5/shutil.py, line 132, in copytree except WindowsError: NameError: global name 'WindowsError' is not defined Tested on ubuntu Feisty and a newly installed Hardy-beta. -- components: Library (Lib) messages: 64930 nosy: jerome.chabod severity: normal status: open title: shutil: NameError (WindowsWrror) when moving from ext3 to fat32 under linux type: crash versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2549 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2549] shutil: NameError (WindowsError) when moving from ext3 to fat32 under linux
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] http://bugs.python.org/issue2549 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2549] shutil: NameError (WindowsError) when moving from ext3 to fat32 under linux
Changes by Trent Nelson [EMAIL PROTECTED]: -- assignee: - Trent.Nelson keywords: +easy nosy: +Trent.Nelson __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2549 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2549] shutil: NameError (WindowsError) when moving from ext3 to fat32 under linux
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 PROTECTED] http://bugs.python.org/issue2549 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2516] Instance methods are misreporting the number of arguments
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 argument (3 given) Is this correct? .. I was hoping for something along the lines of functions raising an ArgumentError (a new subclass of TypeError) that could be trapped by the __call__ slot for bound methods and then reraised with a new argument count. This would be my first choice for a clean solution as well. Since it will require a change to the exception hierarchy, should we discuss a modification to PEP 348 on python-dev? I would rather finish the patch first and then make a concrete proposal. The key is to find a *very* lightweight and minimal solution; .. according to what metric? Are you talking about the amount of code that needs to be changed, the number of API changes or run-time overhead? I don't think run-time overhead is an issue: argument errors are rarely used for flow control because it is hard to predict what a failed attempt to call a function would do. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2516 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2550] SO_REUSEADDR doesn't have the same semantics on Windows as on Unix
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 found after a bit of digging is that Windows doesn't raise EADDRINUSE socket.errors when you bind() two sockets to identical host/ports *IFF* SO_REUSEADDR has been set as a socket option. Decided to brighten up my tube journey into work this morning by reading the Gospel's take on the situation. As per the 'SO_REUSEADDR and SO_REUSEPORT Socket Options' section in chapter 7.5 of Stevens' UNIX Network Programming Volume 1 (2nd Ed): With TCP, we are never able to start multiple servers that bind the same IP address and same port: a completely duplicate binding. That is, we cannot start one server that binds 198.69.10.2 port 80 and start another that also binds 198.69.10.2 port 80, even if we set the SO_REUSEADDR socket option for the second server. So, it seems at least Windows isn't adhering to this, at least on XP and Server 2008 with 2.5-2.6. I've patched test_socket.py to explicitly test for this situation -- as expected, it passes on Unix (tested on FreeBSD in particular), and fails on Windows. I'd like to commit this to trunk to see if any of the buildbots for different platforms match the behaviour of Windows. -- assignee: Trent.Nelson components: Library (Lib), Windows files: test_socket.py.patch keywords: 26backport, patch messages: 64933 nosy: Trent.Nelson priority: high severity: normal status: open title: SO_REUSEADDR doesn't have the same semantics on Windows as on Unix type: behavior versions: Python 2.5, Python 2.6, Python 3.0 Added file: http://bugs.python.org/file9939/test_socket.py.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2550 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2537] re.compile(r'((x|y+)*)*') should fail
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 subexpressions still work? I get: re.compile(r'(?:(?:x|y)*)*') Traceback (most recent call last): File stdin, line 1, in module File /usr/lib/python2.5/re.py, line 180, in compile return _compile(pattern, flags) File /usr/lib/python2.5/re.py, line 233, in _compile raise error, v # invalid expression sre_constants.error: nothing to repeat -- nosy: +marketdickinson __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2537 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2296] [PATCH] Tcl/Tk 8.4.16 patches needed to get an x64 Windows build
Changes by Trent Nelson [EMAIL PROTECTED]: -- status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2296 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2221] Py30a3: eval in threaded code raises SystemError
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, line 1, in module
eval('a')
File string, line 1, in module
NameError: name 'a' is not defined
With the subprocess there is an interpreter
error when IDLE applies eval to 'a':
IDLE 3.0a4
eval('a')
Traceback (most recent call last):
File pyshell#0, line 1, in module
eval('a')
SystemError: error return without exception set
I did a cutdown where I ran the eval in a
subprocess and didn't reproduce the error. I
suspect it's thread related (the subprocess
uses its main thread to execute user code, and
another thread to manage the socket connection
to the GUI process).
issue1733757 is suggestive.
This is a 3.0 issue, it doesn't occur in the
trunk.
--
assignee: kbk -
components: +Interpreter Core -IDLE
nosy: +amaury.forgeotdarc
priority: normal - high
title: Py30a3: calltip produces error output to stderr - Py30a3: eval in
threaded code raises SystemError
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2221
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2250] rlcompleter raises Exception on bad input
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 Errors derived from Exceptions (not SystemError and KeyboardInterrupt). while this seems rather drastic I really feel that this step should in no case raise an Exception. I can't possibly think of a situation where someone would want that. Concerning the docs: ...it will try to evaluate anything without obvious side-effects... I would consider raising an exception as a major side-effect so this patch rather brings the code into accordance with the docs than it contradicts them. Added file: http://bugs.python.org/file9940/rlcompleter_Exception.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2250 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2551] Python 2.6a2 on Solaris 10 built with SUN C
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 test_bsddb185 test_bsddb3 test_cd test_cl test_codecmaps_cn test_codecmaps_hk test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw test_ctypes test_curses test_epoll test_gdbm test_gl test_imageop test_imgfile test_kqueue test_linuxaudiodev test_macostools test_normalization test_ossaudiodev test_pep277 test_py3kwarn test_scriptpackages test_socket_ssl test_socketserver test_sqlite test_ssl test_startfile test_tcl test_timeout test_unicode_file test_urllib2net test_urllibnet test_winreg test_winsound test_zipfile64 3 skips unexpected on sunos5: test_tcl test_ssl test_ctypes The ctypes test failed since the _ctypes module did not compile. ... cc -KPIC -xtarget=native -DNDEBUG -xO5 -I. -I/.../tools/Python- 2.6a2/./Include -Ibuild/temp.solaris-2.10-i86pc-2.6/libffi/include - Ibuild/temp.solaris-2.10-i86pc-2.6/libffi -I/.../tools/Python- 2.6a2/Modules/_ctypes/libffi/src -I. -IInclude -I./Include - I/.../tools/Python-2.6a2/Include -I/.../tools/Python-2.6a2 -c .../tools/Python-2.6a2/Modules/_ctypes/_ctypes.c -o build/temp.solaris- 2.10-i86pc-2.6/.../tools/Python-2.6a2/Modules/_ctypes/_ctypes.o build/temp.solaris-2.10-i86pc-2.6/libffi/include/ffitarget.h, line 67: undefined symbol: FFI_DEFAULT_ABI build/temp.solaris-2.10-i86pc-2.6/libffi/include/ffitarget.h, line 68: non-constant enumerator value build/temp.solaris-2.10-i86pc-2.6/libffi/include/ffi.h, line 255: syntax error before or at: __attribute__ build/temp.solaris-2.10-i86pc-2.6/libffi/include/ffi.h, line 255: warning: old-style declaration or incorrect type for: __attribute__ build/temp.solaris-2.10-i86pc-2.6/libffi/include/ffi.h, line 255: warning: syntax error: empty declaration .../tools/Python-2.6a2/Modules/_ctypes/_ctypes.c, line 155: cannot recover from previous errors cc: acomp failed for /.../tools/Python-2.6a2/Modules/_ctypes/_ctypes.c ... The test_ioctl failures seems test related. ... test test_ioctl failed -- Traceback (most recent call last): File /.../tools/Python-2.6a2/Lib/test/test_ioctl.py, line 56, in test_ioctl_signed_unsigned_code_param saved_winsz = fcntl.ioctl(mfd, termios.TIOCGWINSZ, \0*8) IOError: [Errno 22] Invalid argument ... There is no SSL support and Tcl is not installed on this machine. Finally, this failure does not show up in the summary: ... test_parser Expecting 's_push: parser stack overflow' in next line s_push: parser stack overflow ... -- components: Tests messages: 64937 nosy: MrJean1 severity: normal status: open title: Python 2.6a2 on Solaris 10 built with SUN C versions: Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2551 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2551] Python 2.6a2 on Solaris 10 built with SUN C
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 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2551 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1517495] memory leak threading or socketserver module
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 (2.6a2). I attached my results for both. For me it looks like the average memory variations. -- nosy: +okkoto Added file: http://bugs.python.org/file9941/memory2.4.2.csv _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1517495 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1517495] memory leak threading or socketserver module
Changes by Robert Schuppenies [EMAIL PROTECTED]: Added file: http://bugs.python.org/file9942/memory2.6a2.csv _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1517495 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2551] Python 2.6a2 on Solaris 10 built with SUN C
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2552] test_ctypes failed Python 2.6a2 Solaris 10 SUN C
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 -Ibuild/temp.solaris-2.10-i86pc-2.6/libffi/include - Ibuild/temp.solaris-2.10-i86pc-2.6/libffi -I/.../tools/Python- 2.6a2/Modules/_ctypes/libffi/src -I. -IInclude -I./Include - I/.../tools/Python-2.6a2/Include -I/.../tools/Python-2.6a2 -c .../tools/Python-2.6a2/Modules/_ctypes/_ctypes.c -o build/temp.solaris- 2.10-i86pc-2.6/.../tools/Python-2.6a2/Modules/_ctypes/_ctypes.o build/temp.solaris-2.10-i86pc-2.6/libffi/include/ffitarget.h, line 67: undefined symbol: FFI_DEFAULT_ABI build/temp.solaris-2.10-i86pc-2.6/libffi/include/ffitarget.h, line 68: non-constant enumerator value build/temp.solaris-2.10-i86pc-2.6/libffi/include/ffi.h, line 255: syntax error before or at: __attribute__ build/temp.solaris-2.10-i86pc-2.6/libffi/include/ffi.h, line 255: warning: old-style declaration or incorrect type for: __attribute__ build/temp.solaris-2.10-i86pc-2.6/libffi/include/ffi.h, line 255: warning: syntax error: empty declaration .../tools/Python-2.6a2/Modules/_ctypes/_ctypes.c, line 155: cannot recover from previous errors cc: acomp failed for /.../tools/Python-2.6a2/Modules/_ctypes/_ctypes.c ... -- components: Tests messages: 64941 nosy: MrJean1 severity: normal status: open title: test_ctypes failed Python 2.6a2 Solaris 10 SUN C versions: Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2552 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2554] test_ioctl failed Python 2.6a2 Solaris 10 SUN C
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 test_ioctl_signed_unsigned_code_param saved_winsz = fcntl.ioctl(mfd, termios.TIOCGWINSZ, \0*8) IOError: [Errno 22] Invalid argument ... -- components: Tests messages: 64943 nosy: MrJean1 severity: normal status: open title: test_ioctl failed Python 2.6a2 Solaris 10 SUN C versions: Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2554 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2555] test_parser failed Python 2.6a2 Solaris 10 SUN C
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 ... -- components: Tests messages: 64944 nosy: MrJean1 severity: normal status: open title: test_parser failed Python 2.6a2 Solaris 10 SUN C versions: Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2555 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2553] test_ioctrl failed Python 2.6a2 Solaris 10 SUN C
Jean Brouwers [EMAIL PROTECTED] added the comment: This is a duplicate. Please ignore. My apologies. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2553 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2552] test_ctypes failed Python 2.6a2 Solaris 10 SUN C
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2551] Python 2.6a2 on Solaris 10 built with SUN C
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue802310] tkFont may reuse font names
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 this is no longer a problem ? If it should be fixed, are there any suggestions on how to proceed ? -- nosy: +gpolo Tracker [EMAIL PROTECTED] http://bugs.python.org/issue802310 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2553] test_ioctrl failed Python 2.6a2 Solaris 10 SUN C
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 test_ioctl_signed_unsigned_code_param saved_winsz = fcntl.ioctl(mfd, termios.TIOCGWINSZ, \0*8) IOError: [Errno 22] Invalid argument ... -- messages: 64942 nosy: MrJean1 severity: normal status: open title: test_ioctrl failed Python 2.6a2 Solaris 10 SUN C __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2553 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2537] re.compile(r'((x|y+)*)*') should fail
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 xyyzy.sub(/((x|y)*)*/, (\\1, \\2)) = (, y)zy xyyzy.sub(/((x|y+)*)*/, (\\1, \\2)) = (, yy)zy DB1 $_ = 'xyyzy'; s/((x|y)*)*/(\1 \2)/; print ( )zy DB2 $_ = 'xyyzy'; s/((x|y+)*)*/(\1 \2)/; print ( yy)zy Ruby's behavior seems best to me. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2537 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue869780] curselection() in Tkinter.py should return ints
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 Tracker [EMAIL PROTECTED] http://bugs.python.org/issue869780 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2221] Py30a3: eval in threaded code raises SystemError
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 exception info (which is bad). To correct the problem, I it is enough to calls to PyErr_Fetch/PyErr_Restore. This happens only with Idle, probably because the subprocess redirected its stdout to a pseudo-file that does not support flush(). __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2221 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2221] Py30a3: eval in threaded code raises SystemError
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2548] Undetected error in exception handling
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 problem because PyEval_CallObject did not check the recursion limit. Different solutions I can think of: - use a prebuilt exception: not possible if we still want an error message containing the context. - in PyErr_NormalizeException, PyEval_CallObject is too generic. We could have a special path for exception types deriving from BaseException: directly call the constructor. -- nosy: +amaury.forgeotdarc __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2548 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1179] [CVE-2007-4965] Integer overflow in imageop module
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 blocker __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1179 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2221] Py30a3: eval in threaded code raises SystemError
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 problem only occurred when IDLE was running its subprocess. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2221 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2506] Line tracing of continue after always-taken if is incorrect
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, generate annotated statement coverage listings, print caller/callee relationships and list functions executed during a program run. This could be augmented with a general statement that the effect of certain statements may get computed during compilation and not appear in the runtime trace -- or a more specific statement about continue, break, and whatever else. AS for continue.py, it seems that the apparent non-execution of a continue line indicates one of two possible problems. 1. The if statement is equivalent to 'if True:', at least for the intended domain of input, hence redundant, and hence could/should be removed. 2. Otherwise, the inputs are incomplete as far as testing the effect of not taking the if-branch, and hence could/should be augmented. Either way, it seems to me that the lack of runtime execution of continue, coupled with better documentation, could usefully point to possible action. -- nosy: +tjreedy __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2506 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2515] Segfault while operating on closed sqlite3 cursor.
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2515] Segfault while operating on closed sqlite3 cursor.
Changes by Neal Norwitz [EMAIL PROTECTED]: -- priority: - release blocker __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2515 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2526] str.format() :n format does not appear to work
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2546] Python-2.5.2: crash in visit_decref () at Modules/gcmodule.c:270
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 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2546 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2548] Undetected error in exception handling
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 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2548 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2548] Undetected error in exception handling
Changes by Daniel Diniz [EMAIL PROTECTED]: -- nosy: +ajaksu2 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2548 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2555] test_parser failed Python 2.6a2 Solaris 10 SUN C
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2551] Python 2.6a2 on Solaris 10 built with SUN C
Martin v. Löwis [EMAIL PROTECTED] added the comment: Thanks! -- resolution: - duplicate status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2551 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2553] test_ioctrl failed Python 2.6a2 Solaris 10 SUN C
Changes by Martin v. Löwis [EMAIL PROTECTED]: -- resolution: - duplicate status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2553 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2538] memoryview of bytes is not readonly
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 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
