[issue7932] print statement delayed IOError when stdout has been closed

Martin v. Löwis added the comment: This is not a bug. The output stream gets buffered, and that it is closed is only detected when a flush is attempted. Use the -u option if you want unbuffered stdout. It is, however, a bug that Python 2.6 apparently fails to flush the output at all; Python

[issue7932] print statement delayed IOError when stdout has been closed

New submission from tholzer : When printing to a closed stdout file descriptor, the print statement only raises an IOError at character 8192. The expected behaviour is that IOError gets raised immediately (i.e. on the first character). Compare this behaviour to writing to a closed sys.stderr.

[issue7930] pydoc.stripid doesn't strip ID in py25, py26, py31

New submission from Michael Newman : I found that pydoc.stripid doesn't strip the ID in Python 2.5, 2.6, and 3.1. I assume the problem is probably present in 2.7 and 3.2/dev. For a little history, see this older issue back for Python 2.3: http://bugs.python.org/issue934282 The following exampl

[issue5651] OS X Installer: add checks to ensure proper Tcl configuration during build

Katrine Whiteson added the comment: Hi, Wow, thank you for noticing this. I tried to install python 2.6.4 with the mac dmg, but couldn't figure out where it was installed. I hunted around and made a link to a python 2.6 that I found - it must have been a previous version. Now I have a f

[issue7926] Stray parentheses() in context manager "what's new" doc

Edward Welbourne added the comment: Nice :-) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue7788] segfault when deleting from a list using slice with very big `step' value

Mark Dickinson added the comment: Yes, adding carefully placed (size_t) casts seems like the right way to solve the problem. I've fixed all (I think) the warnings in r78183, r78184, r78189. I also fixed one case (unrelated to this issue) of potential undefined behaviour from signed overflow

[issue7926] Stray parentheses() in context manager "what's new" doc

Georg Brandl added the comment: Thanks, should be fine now in r78188. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs

[issue7928] String formatting: grammar wrongly limits [index] to integer

Changes by Georg Brandl : -- assignee: georg.brandl -> eric.smith nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing

[issue7923] StreamHandler and FileHandler located in logging, not in logging.handlers

Vinay Sajip added the comment: These changes have already been made in trunk (see r68624, r76869), just not backported to release26-maint. -- resolution: -> wont fix status: open -> closed ___ Python tracker

[issue7926] Stray parentheses() in context manager "what's new" doc

Edward Welbourne added the comment: The third change removes the early uses of "object" from: Finally, the closing(object)() function returns object so that it can be bound to a variable, and calls object.close at the end of the block. leaving the last use (object.close) as a dangling referen

[issue7928] String formatting: grammar wrongly limits [index] to integer

New submission from Edward Welbourne : http://docs.python.org/library/string.html#formatstrings field_name::= (identifier | integer) ("." attribute_name | "[" element_index "]")* element_index ::= integer Subsequent text indicates __getitem__() is used but does not overtly say that

[issue7927] SSL socket is not closed properly

New submission from Péter Szabó : Here is how to reproduce: import socket import ssl sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM) sslsock = ssl.SSLSocket(sock) assert sslsock._sslobj is None sslsock.connect(('www.gmail.com', 443)) assert isinstance(sslsock._sslobj, socket._ssl.SSLTyp

[issue7926] Stray parentheses() in context manager "what's new" doc

Georg Brandl added the comment: Fixed in r78182. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bug