[issue4630] IDLE no longer respects .Xdefaults insertOffTime

Mark Summerfield added the comment: Py2.6: idlelib/EditorWindow.py change line 110 from: width=self.width, to: width=self.width, insertofftime=0, Py3.0 apply the same change to line 112 This will switch off cursor blink (and annoy people who want cursor blink). So really instead of setting it

[issue5551] os.path.ismount take a cross-device symlink for a mountpoint

New submission from Jürgen A. Erhard : Confirmed to exist in 2.6.1 (r261:67515) and 3.0 (r30:67503). Seems to have been introduced somewhere in the 2.5 timeline, as 2.4 doesn't show this bug. -- components: Library (Lib) messages: 84060 nosy: jae severity: normal status: open title: os.

[issue1396258] KeyboardInterrupt prevents return to Windows console

Vernon Cole added the comment: A quick test on Vista shows that this problem is not present in Python 2.6 nor 3.0. -- ___ Python tracker ___ __

[issue5550] urllib2 use of opener.addheaders

New submission from cocobear : take a look at following code: import urllib2 headers = [("Content-Type","application/oct-stream"),] opener = urllib2.build_opener() opener.addheaders = headers urllib2.install_opener(opener) print "after install_opener" ret = opener.open('http://www.google.com',

[issue5129] indentation in IDLE 2.6 different from IDLE 2.5, 2.4 or vim

Guilherme Polo added the comment: Patch attached, if someone can create a test for it then that would be very good. -- keywords: +patch Added file: http://bugs.python.org/file13404/fix_5129.diff ___ Python tracker

[issue4630] IDLE no longer respects .Xdefaults insertOffTime

Mehmet Köse added the comment: Would you please share that code with us. -- nosy: +decaf ___ Python tracker ___ ___ Python-bugs-list m

[issue5549] PyModule_Create and PyModuleDef are undocumented

Daniel Stutzbach added the comment: That was quick! Thanks! :-) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue5129] indentation in IDLE 2.6 different from IDLE 2.5, 2.4 or vim

Guilherme Polo added the comment: You do not need IDLE to reproduce the problem: import Tkinter text = Tkinter.Text() text.pack() text.insert('1.0', 'class C:\n\tdef m(self, c):\n' 'if c:\nc = False\n' '\t\t\tc = False\n

[issue5540] "file objects" in python 3 tutorial

Benjamin Peterson added the comment: 2009/3/23 David W. Lambert : > > David W. Lambert added the comment: > > File objects should not be discussed in the tutorial to emphasize that > the file type is gone. > > File objects should be in the tutorial as a useful familiar concept. I don't underst

[issue5129] indentation in IDLE 2.6 different from IDLE 2.5, 2.4 or vim

Guilherme Polo added the comment: It turns out that the problem is not in differences between IDLE in 2.5 and the one in 2.6, instead it is caused by the usage of Tk 8.5 by IDLE 2.6 (included in the Windows package). Changing to Tk 8.4, IDLE 2.6 displays in the same way as 2.5 (tested on Linux w

[issue5129] indentation in IDLE 2.6 different from IDLE 2.5, 2.4 or vim

Guilherme Polo added the comment: I just tried it here under Windows XP (using python 2.6.1 from python.org) and the untabify dialog showed up with 8 as the default number of columns per tab (although there are at least two bugs with this dialog: i) I clicked on cancel but it still untabified th

[issue2259] Poor support other than 44.1khz, 16bit audio files?

Changes by R. David Murray : -- keywords: +easy stage: -> test needed type: crash -> behavior versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 ___ Python tracker ___ ___

[issue2266] Missing documentation about old/new-style classes

R. David Murray added the comment: I think this can be closed as 'out of date'. The language reference chapter has a section on old and new style classes, and in the tutorial section the reference to 'new style class' is hyperlinked to a glossary entry that in turn contains a pointer to that la

[issue5547] The Py_InitModule functions no longer exist, but remain in the docs

Benjamin Peterson added the comment: Fixed in r70576. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue5549] PyModule_Create and PyModuleDef are undocumented

New submission from Benjamin Peterson : Fixed in r70576. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Garrett Cooper added the comment: Unfortunately we're still stuck on 2.4.5 because I don't have enough buy-in from tech leads and architects to upgrade right now -_-... Good idea though :] *stores for later*. -- ___ Python tracker

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Kumar McMillan added the comment: For the record, I too have been plagued by failing setUp's :( and the pattern you describe is not uncommon. I was just pointing out that changing the semantics of tearDown() will affect a lot of existing code. As with any backwards incompatible change the effo

[issue5549] PyModule_Create and PyModuleDef are undocumented

Changes by Daniel Stutzbach : -- assignee: georg.brandl components: Documentation nosy: georg.brandl, stutzbach severity: normal status: open title: PyModule_Create and PyModuleDef are undocumented versions: Python 3.0, Python 3.1 ___ Python tracker

[issue5548] In the tutorial, PyMODINIT_FUNC is shown as having a return type of void rather than PyObject *

New submission from Daniel Stutzbach : PyMODINIT_FUNC functions should return the module object or NULL on error. Or at least that what it looks like the core modules are doing. ;-) -- assignee: georg.brandl components: Documentation messages: 84045 nosy: georg.brandl, stutzbach severit

[issue5547] The Py_InitModule functions no longer exist, but remain in the docs

New submission from Daniel Stutzbach : Py_InitModule, Py_InitModule3, etc. are mentioned in the docs (including the extending tutorial!), but no longer exist. -- assignee: georg.brandl components: Documentation messages: 84044 nosy: georg.brandl, stutzbach severity: normal status: open t

[issue5546] PyDict_SetItemString mentions PyString_FromString which does not exist

Benjamin Peterson added the comment: Fixed in r70556. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue1034053] unittest.py patch: add skipped test functionality

Benjamin Peterson added the comment: Committed my patch in r70555. -- resolution: -> accepted status: open -> closed ___ Python tracker ___ __

[issue5546] PyDict_SetItemString mentions PyString_FromString which does not exist

New submission from Daniel Stutzbach : The documentation for PyDict_SetItemString contains the text "The key object is created using PyString_FromString(key)". However, PyString_FromString has been removed in Python 3. Perhaps it should read PyUnicode_FromString? -- assignee: georg.bra

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Garrett Cooper added the comment: Excellent point Kumar. Here's what I'm trying to accomplish... I'm a part of a team that's testing out IOSd on an up and coming Unix foundation platform. This requires starting up a series of services, ensuring that they have come up, and then login to the IOS

[issue5545] multiprocessing: switch to autoconf detection of platform values

Roumen Petrov added the comment: What about AC_CHECK_FUNC* macros ? -- nosy: +rpetrov ___ Python tracker ___ ___ Python-bugs-list mail

[issue5543] sys.last_type missing

Benjamin Peterson added the comment: Trundle, you are correct. Reverted in r697553. -- resolution: fixed -> invalid ___ Python tracker ___ ___

[issue5543] sys.last_type missing

Trundle added the comment: Is the fix really correct? The documentation clearly states about `sys.last_type`: "These three variables are not always defined; they are set when an exception is not handled and the interpreter prints an error message and a stack traceback." And there is already `tra

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Kumar McMillan added the comment: fwiw, changing tearDown() so that it executes unconditionally will break a countless number of test suites. No test suite since the dawn of unittest has been designed to tearDown() what may not have been setUp() correctly. in other words, this is how [in my ex

[issue5544] test_fileio fails on windows MSVC Assertion

Antoine Pitrou added the comment: It is not strictly speaking "an error" which is causing the double close... It's the deliberate behaviour of a test I have added to check that errno is correctly set on the raised IOError when calling close() on a FileIO object whose handle has already been clos

[issue5541] File's current position inconsistent with 'a+' mode

Martin v. Löwis added the comment: In 2.x, the mode will do whatever the C library does; this is as it ought to be. Standard C lets it explicitly implementation-defined whether the file position pointer is initially at the beginning or at the end of a file when the file is opened for append. Any

[issue2889] curses for windows (alternative patch)

Changes by Paul Moore : -- nosy: +pmoore ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue5543] sys.last_type missing

Benjamin Peterson added the comment: Fixed in r70552. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue5544] test_fileio fails on windows MSVC Assertion

Antoine Pitrou added the comment: I wonder whether a magic assertion-disabling spell is needed around the call to close() in _fileio.c. Kristjan, do you have any insights on this? -- nosy: +krisvale, loewis ___ Python tracker

[issue5544] test_fileio fails on windows MSVC Assertion

Andreas Schawo added the comment: I'm afraid your patch doesn't solve it. I got the same popup: Debug Assertion Failed! Program: .\python_d.exe File: f:\dd\vctoools\crt_bld\self_x86\crt\src\close.c Line: 48 Expression: (_osfile(fh) & FOPEN) It failed while running testErrnoOnClose. I'm u

[issue5516] equality not symmetric for subclasses of datetime.date and datetime.datetime

Jess Austin added the comment: The attached patch fixes this issue, and updates the tests. Contrary to my initial impression, it seems that a previous developer knew of this behavior and thought it correct; see the comment of the test I deleted. I left memcmp() in. -- keywords: +patch

[issue5463] Remove deprecated features from struct module

Changes by Mark Dickinson : -- assignee: -> marketdickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue5512] Streamline integer division

Mark Dickinson added the comment: Applied, r70542 and r70547. -- resolution: -> accepted status: open -> closed ___ Python tracker ___ __

[issue4688] GC optimization: don't track simple tuples and dicts

Antoine Pitrou added the comment: Thanks for the review, by the way! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue5541] File's current position inconsistent with 'a+' mode

Changes by Antoine Pitrou : -- priority: -> normal type: -> behavior versions: +Python 2.7 -Python 2.5 ___ Python tracker ___ ___ Pyt

[issue5541] File's current position inconsistent with 'a+' mode

Antoine Pitrou added the comment: The right answer IMO is that the current position should be set to the end of the file, since it is opened in "append" mode. What happens actually is that, on some systems, the position is implicitly set to the end of the file on the first write() rather than wh

[issue4688] GC optimization: don't track simple tuples and dicts

Antoine Pitrou added the comment: I've added tracking statistics for tuples, documentation for gc.is_tracked(), and changed _Py*_Optimize to _Py*_MaybeUntrack on a suggestion by Benjamin. Committed to trunk in r70546. -- resolution: accepted -> fixed status: open -> closed

[issue5544] test_fileio fials on windows MSVC Assertion

Hirokazu Yamamoto added the comment: I cannot test this because I don't have recent VC, but last week change to _fileio.c is this. http://svn.python.org/view/python/branches/py3k/Modules/_fileio.c?r1=70187&r2=70352 On windows, lseek was used before, but _lseeki64 in portable_lseek is used now.

[issue5545] multiprocessing: switch to autoconf detection of platform values

Christian Heimes added the comment: I've correct some smaller issues and integrated the autoconf code into multiprocessing and setup.py A working patch is appended. -- keywords: +patch Added file: http://bugs.python.org/file13402/mp_autoconf.patch __

[issue1413379] Popened file object close hangs in latest Cygwin update

Eric McRae added the comment: Had forgotten about this. Just re-ran my test and it works fine now. My current versions are Python 2.5.1 and Tk 8.4 So long and thanks for all the fish... -- status: open -> closed versions: +Python 2.5 -Python 2.6 _

[issue5435] test_httpservers on Debian Testing

Facundo Batista added the comment: CGI tests shouldn't be run as root, it seems, as it breaks the inherent protection. -- nosy: +facundobatista resolution: -> invalid status: open -> closed ___ Python tracker

[issue5545] multiprocessing: switch to autoconf detection of platform values

New submission from Jesse Noller : See mail thread: http://mail.python.org/pipermail/python-dev/2009-March/087418.html And Christian's checkin to the back port: http://code.google.com/p/python-multiprocessing/source/detail?r=64# Need to take into the account information here (for my own notes):

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Jean-Paul Calderone added the comment: /Any/ addCleanup that is successfully executed should cause the cleanup function to be called. Otherwise you have to define all your cleanup twice, and that's no fun. -- ___ Python tracker

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Garrett Cooper added the comment: Before I forget though -- should the requirements for the functionality be that it be called strictly in setUp on failure, or should it be executed as a part of tearDown as well? Thanks! -- ___ Python tracker

[issue5544] test_fileio fials on windows MSVC Assertion

Antoine Pitrou added the comment: Can you find out in which test case the assertion is triggered? Also, is there more information in the error message itself? -- components: +Library (Lib) priority: -> critical type: -> behavior ___ Python tracker

[issue5544] test_fileio fials on windows MSVC Assertion

New submission from Andreas Schawo : test_fileio fails on windows with MSVC "Debug Assertion failed" message since last week. -- components: Tests messages: 84015 nosy: andreas.schawo, pitrou severity: normal status: open title: test_fileio fials on windows MSVC Assertion versions: Pytho

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Garrett Cooper added the comment: Ok, sounds good then ;). I'll open another issue with the enhancement later on this week. Cheers! -- ___ Python tracker ___ ___

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Steve Purcell added the comment: Sounds good to me. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Jean-Paul Calderone added the comment: > And maybe the addCleanup components could be a stack of callable objects? Yea, that's handy. My example didn't show it, but that's what trial implements. -- ___ Python tracker

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Garrett Cooper added the comment: And maybe the addCleanup components could be a stack of callable objects? This would make life easier for folks like me and would make the overall flow much cleaner / clearer as it would allow us to break things down into atomic steps which could be reverted in

[issue5435] test_httpservers on Debian Testing

Manuel Kaufmann added the comment: I think it isn't a problem / bug, rather than it's a protection method to don't execute this test or cgi stuff with root user. In the middle, it change a userid to 'nobody', then if you are logged in as root, it can change the userid and then you don't have pe

[issue5463] Remove deprecated features from struct module

Changes by Andreas Schawo : Removed file: http://bugs.python.org/file13304/struct_overflow_patch.diff ___ Python tracker ___ ___ Python-bugs-li

[issue5463] Remove deprecated features from struct module

Andreas Schawo added the comment: I removed definition of _PY_STRUCT_RANGE_CHECKING. The test_standard_integers now expects struct.errors when there are out of range values (should have been part of my last patch). So test_1229380 is now obsolete. -- Added file: http://bugs.python.org

[issue5540] "file objects" in python 3 tutorial

David W. Lambert added the comment: File objects should not be discussed in the tutorial to emphasize that the file type is gone. File objects should be in the tutorial as a useful familiar concept. -- ___ Python tracker

[issue5435] test_httpservers on Debian Testing

Hirokazu Yamamoto added the comment: Hmm, I'm using coLinux with root user. (default) Maybe that's difference. -- ___ Python tracker ___ _

[issue5435] test_httpservers on Debian Testing

Manuel Kaufmann added the comment: I downloaded py3k branch and ran the tests with a regular user. All test pass OK. SVN Revision: 70469 -- nosy: +humitos Added file: http://bugs.python.org/file13400/httpservers_test ___ Python tracker

[issue5178] Add context manager for temporary directory

Nick Coghlan added the comment: Unassigning for the moment - I'm still interested in the idea, but the referencing-globals-at-shutdown problem means it isn't going to be the straightforward review-and-commit that I original thought this patch was going to be. I'll still try to get to it before

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Jean-Paul Calderone added the comment: Here's one: class ReactorShutdownInteraction(unittest.TestCase): """Test reactor shutdown interaction""" def setUp(self): """Start a UDP port""" self.server = Server() self.port = reactor.listenUDP(0, self.server, interface

[issue1379416] email.Header encode() unicode P2.6

Jan Novak added the comment: I made some new tests in P2.6.1 >>> import email.charset >>> c=email.charset.Charset('utf-8') >>> print c.input_charset, type(c.input_charset) utf-8 >>> print c.output_charset, type(c.output_charset) utf-8 but >>> c=email.charset.Charset('iso-8859-2') >>> print

[issue5543] sys.last_type missing

New submission from Alexandru V. Mosoi : `sys.last_type' is missing and thus, traceback.print_last() is not working. $ python Python 2.6.1 (r261:67515, Dec 7 2008, 18:56:39) [GCC 4.3.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> try: ra

[issue5542] Socket is closed prematurely in httplib, if server sends response before request body has been sent

Jason Davies added the comment: Note: in case I didn't make it clear, the fix is to remove the offending try/except handler and let the broken pipe error propagate. -- ___ Python tracker ___

[issue5542] Socket is closed prematurely in httplib, if server sends response before request body has been sent

New submission from Jason Davies : I came across this bug when trying to use CouchDB-Python to PUT an attachment using HTTP authentication (using the httplib2 library). Essentially what httplib2 does is this: 1. Attempt PUT with no auth credentials 2. If a 401 response is received, try again wi

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Garrett Cooper added the comment: I agree with you guys to a certain extent, but doing so only complicates my setup procedure to the extent that I'm calling a lot of my teardown code in a dumb manner, unless I actually kept track of how far into the setup process I got before everything went awr

[issue5538] tearDown in unittest should be executed regardless of result in setUp

Steve Purcell added the comment: Indeed -- if some of the setUp code is likely to fail, that should be handled right there in setUp, by reversing any other setup code that may have executed. It's harder to write a tearDown that will work reliably for any partially successful setUp.

[issue5541] File's current position inconsistent with 'a+' mode

New submission from Lukas Lueg : The file pointer's behaviour after opening a file in 'a+b' mode is not consistent among platforms: The pointer is set to the beginning of the file on Linux and to the end of the file on MacOS. You have to call .seek(0) before calling .read() to get consistent beha