[issue481171] Hang using files named prn.txt, etc

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue6574] List the __future__ features in a table

New submission from Ezio Melotti : The documentation about the __future__ features [1] only lists the features available for that particular version, without specifying when they were added and their effects. It would be nice to have a table with |feature|version added|effect|. A better place for

[issue6567] Make inf be almost equal to inf

Mark Dickinson added the comment: Sounds good to me. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue1820] Enhance Object/structseq.c to match namedtuple and tuple api

Changes by Ori Avtalion : -- nosy: +salty-horse ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue6575] Can't download docs

New submission from Jan Kaliszewski : http://docs.python.org/3.1/download.html (available both with 'Download these documents' link @docs and 'Download Current Python 3.1 Documentation' link @http://www.python.org/doc/) doesn't contain links to packed docs, but text for dev-releases: "We don'

[issue1424152] urllib/urllib2: HTTPS over (Squid) Proxy fails

Senthil added the comment: Agreed to the suggestions made by Greg. The fix is now backported. For Py2.6 in the revision 74203. For Py3k in the revision 74204. Closing this issue. -- status: open -> closed ___ Python tracker

[issue6574] List the __future__ features in a table

Robert Lehmann added the comment: I composed a list of __future__ features and linked the respective PEPs. Even though the language reference would be a better place to store such general information (being PEP'd and all) I found the library reference's __future__.py documentation to be a clean

[issue1448934] urllib2+https+proxy not working

Senthil added the comment: Well, the fix for this same as that for Issue1424152. Closing this issue as it is already handled. -- resolution: -> duplicate status: open -> closed ___ Python tracker __

[issue6576] re docs: wrong link targets

New submission from Jan Kaliszewski : Some of links in re docs should lead to RegexObject.match()| RegexObject.search() method but lead to re.match()|re.search() module function. These are the places in 2.6 docs (in 2.7-3.2 versions' you'll find the bug in analogous places): http://docs.pytho

[issue6576] re docs: wrong link targets

Georg Brandl added the comment: Thanks for the report, I fixed the references (and a few to compile()) in r74205. -- resolution: -> fixed status: open -> closed ___ Python tracker _

[issue6577] Links wrongly targeting to builtin functions' instead of module functions/methods

New submission from Jan Kaliszewski : The problem can be found in many places in docs -- tipically, where there is a function/method with name identical to builtin name (or sometimes to another function/method within the same module -- see: #6575): links leads to te latter but should lead to t

[issue6575] Can't download docs

Georg Brandl added the comment: Fixed in r74206; the online version should be updated soon. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue6578] 2 problems with 'Docs for other versions' section on left HTML docs sidebar

New submission from Jan Kaliszewski : * In 2.6 the content of that section isn't up to date (3.1 is descripted as 'in development') * In 3.0 there is no that section. -- messages: 90945 nosy: zuo severity: normal status: open title: 2 problems with 'Docs for other versions' section on

[issue6578] 2 problems with 'Docs for other versions' section on left HTML docs sidebar

Changes by Jan Kaliszewski : -- assignee: -> georg.brandl components: +Documentation nosy: +georg.brandl ___ Python tracker ___ ___ Py

[issue6579] No update about automatic numbering of fields in format strings (e.g. 'A {} with {} buttocks')

New submission from Jan Kaliszewski : As we can read in http://docs.python.org/3.1/whatsnew/3.1.html#other- language-changes: The fields in format() strings can now be automatically numbered: >>> 'Sir {} of {}'.format('Gallahad', 'Camelot') 'Sir Gallahad of Camelot' Formerly, the string wo

[issue6577] Links wrongly targeting to builtin functions' instead of module functions/methods

Georg Brandl added the comment: I made an exhaustive search for all builtins; should now be fixed in r74207. Thanks for making me do it properly :) -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue6579] No update about automatic numbering of fields in format strings (e.g. 'A {} with {} buttocks')

Georg Brandl added the comment: The 2.6 one looks fine to me; 3.2 is correctly marked as in development there. I don't care about 3.0; it's not supported anymore. -- resolution: -> works for me status: open -> closed ___ Python tracker

[issue6579] No update about automatic numbering of fields in format strings (e.g. 'A {} with {} buttocks')

Georg Brandl added the comment: Argh, of course it's even more important to point to the current version for 3.0... fixed in r74208. -- ___ Python tracker ___ ___

[issue6579] No update about automatic numbering of fields in format strings (e.g. 'A {} with {} buttocks')

Changes by Georg Brandl : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/opti

[issue6579] No update about automatic numbering of fields in format strings (e.g. 'A {} with {} buttocks')

Changes by Georg Brandl : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/opti

[issue6578] 2 problems with 'Docs for other versions' section on left HTML docs sidebar

Georg Brandl added the comment: The 2.6 one looks fine to me; 3.2 is correctly marked as in development there. Added the section to 3.0 branch in r74208. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue6579] No update about automatic numbering of fields in format strings (e.g. 'A {} with {} buttocks')

Georg Brandl added the comment: (Sorry for my confusion, reopening.) -- assignee: georg.brandl -> eric.smith nosy: +eric.smith resolution: works for me -> status: closed -> open ___ Python tracker

[issue2698] Extension module build fails for MinGW: missing vcvarsall.bat

Changes by Hagen Fürstenau : -- nosy: +hagen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue6580] No deprecation warning for list comprehension leak conflict

New submission from Michael R Bax : PEP 289 states that "Python 2.4 and beyond should issue a deprecation warning if a list comprehension's loop variable has the same name as a variable used in the immediately surrounding scope". But no warning is shown when running for x in [ 0 ]: print

[issue1820] Enhance Object/structseq.c to match namedtuple and tuple api

Ori Avtalion added the comment: For those who missed it, the patch that was committed in r59967 was quickly reverted in r59970 with the comment: "Temporarily revert 59967 until GC can be added." Raymond, can you please explain what was missing from the patch? -- _

[issue2636] Regexp 2.7 (modifications to current re 2.2.2)

Matthew Barnett added the comment: issue2636-20090726.zip is a new implementation of the re engine. It replaces re.py, sre.py, sre_constants.py, sre_parse.py and sre_compile.py with a new re.py and replaces sre_constants.h, sre.h and _sre.c with _re.h and _re.c. The internal engine no longer

[issue6581] inspect.py sys._getframe patch for Python 2.6

New submission from Michael Foord : Patch for inspect.py so that it will import correctly even if sys._getframe is unavailable. Without this patch inspect can't be imported under IronPython 2.6 (breaking basic features like help) when started without Python stack frame support. The same fix is

[issue6581] inspect.py sys._getframe patch for Python 2.6

Michael Foord added the comment: hmm... the lambda should probably take an argument like sys._getframe. -- ___ Python tracker ___ ___

[issue1721862] email.FeedParser.BufferedSubFile improperly handles "\r\n"

Neil Tallim added the comment: Attached a patch containing a unit test based on Sye van der Veen's example and a solution for this problem. Written against Python 2.6 (trunk), r74214, which was current at the time of submission. This is my first patch, so please let me know if I did something

[issue6499] Can't import xmlrpclib, DocXMLRPCServer and SimpleXMLRPCServer when zlib is not available

Kristján Valur Jónsson added the comment: Ah, so this is an interpreter shutdown issue, it seems. Something is causing this thread to not exit until the application exits and that can cause all sorts of weird race conditions. I wonder why that is happening. There must be an issue with test_v

[issue6581] inspect.py sys._getframe patch for Python 2.6

Michael Foord added the comment: Committed in revision 74215 & revision 74216. -- resolution: -> accepted status: open -> closed ___ Python tracker ___ _

[issue6499] Can't import xmlrpclib, DocXMLRPCServer and SimpleXMLRPCServer when zlib is not available

Kristján Valur Jónsson added the comment: No, sorry. You have just introduced the race condition by putting a print after the evt.set(). Setting the event causes the main thread to exit python and so anything after that line will likely not work. In fact, this is probably the reason why we

[issue2636] Regexp 2.7 (modifications to current re 2.2.2)

Georg Brandl added the comment: Sounds like this is an awesome piece of work! Since the patch is obviously a very large piece and will be hard to review, may I suggest releasing the new engine as a standalone package and spreading the word, so that people can stress-test it? By the time 2.7 is

[issue6106] read_until

Jack Diederich added the comment: fixed in r74217 My thanks to everyone who contributed to this bug. "irek" if you let me know your name I'll add it to Misc/ACKS as well. PS, The additional testcase is not ideal; it tests the bad behavior by hooking into the debug output instead of testing t

[issue6582] test_telnetlib doesn't test Telnet.write

New submission from Jack Diederich : test/test_telnetlib.py has zero tests for the telnetlib.Telnet.write method. -- assignee: jackdied messages: 90963 nosy: jackdied severity: normal status: open title: test_telnetlib doesn't test Telnet.write versions: Python 2.7, Python 3.2 _

[issue5188] telnetlib process_rawq buffer handling is confused

Jack Diederich added the comment: between r71434 and r74217 this should be fixed for 3.2. Marking as closed. -- resolution: -> fixed status: open -> closed ___ Python tracker _

[issue1360221] telnetlib expect() and read_until() do not time out properly

Jack Diederich added the comment: this was fixed in r47215 (circa 2006). Marking closed. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue1772794] Telnetlib dosn't accept u'only ascii'

Jack Diederich added the comment: Marking closed/won't fix. ASCII strings are the byte-ish type in 2.x so we should expect the caller to convert down from unicode when sending bytes over the wire. -- resolution: -> wont fix status: open -> closed _

[issue6582] test_telnetlib doesn't test Telnet.write

Jack Diederich added the comment: Marking as easy. What needs to be done is to add a small fake socket class that redefines socket.sendall(self, bytes) to capture the args to sock.sendall so it can be assertEqual'd to the expected bytes. class SocketSendall(socket.socket): _raw_sent = b''

[issue3071] The ValueError raised by failing to unpack sequence should have more information.

Jack Diederich added the comment: The code that raises the error is in ceval.c which is a critical path. The raise is done as soon the iterator has one more item than is needed (see Daniel Diniz's comments on infinite iterators). While the check could return more useful information for known n

[issue2874] Remove use of the stat module in the stdlib

Jack Diederich added the comment: The stat module wasn't deprecated in 3.1, so is this now a non-issue? If not, is it related to issue#1820? -- nosy: +jackdied ___ Python tracker __

[issue2874] Remove use of the stat module in the stdlib

Brett Cannon added the comment: At this point it is a nice idea that no one wants to deal with to make happen. Dropping the priority but leaving open for now until I get around to making a final decision as to whether to just give up on this to finally allow closure on PEP 3108 once profile/c

[issue6550] asyncore incorrect failure when connection is refused and using async_chat channel

Changes by R. David Murray : -- nosy: +josiahcarlson priority: -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue6561] Regex '\d' should not match unicode category 'No'.

R. David Murray added the comment: It may be redundant, but it is also more technically accurate. I'm -0 on your proposed rephrasing, and trust Mark to make the right decision :) -- nosy: +r.david.murray ___ Python tracker

[issue3071] The ValueError raised by failing to unpack sequence should have more information.

Jean-Paul Calderone added the comment: Here's a patch implementing part of the requested feature. pystones cannot tell the difference between tr...@head with or without this patch applied. Both report a maximum of 78125 pystones/second/ -- keywords: +patch nosy: +exarkun Added file: h

[issue1194378] sendmsg() and recvmsg() for C socket module

Ezio Melotti added the comment: Closing this as duplicate of #6560. -- nosy: +ezio.melotti resolution: -> duplicate stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___

[issue3071] The ValueError raised by failing to unpack sequence should have more information.

Jack Diederich added the comment: I was looking at 3.x, JP's patch is relative to 2.x and takes a little more unpacking (a couple function calls more) but looks to me to be the same. In 2.x unpack_iterable() sets/returns an error once one item more than is required is received. It doesn't give

[issue6583] 2to3 fails to fix test.test_support

New submission from Joe Amenta : PEP 3108 states that test.test_support was renamed to test.support as a part of the Standard Library Reorganization process. However... 2to3 does not refactor (or even warn about) test.test_support. Simply adding "test.test_support": "test.support", into the MA

[issue6584] gzip module has no custom exception

New submission from Sridhar Ratnakumar : Much like zipfile.BadZipfile, we need a base custom exception for the gzip module. At least, catch gzip-related exceptions and throw a tarfile.TarError when used *via* tarfile.*. See the following example (the exception escaped the "try... except tarfi

[issue6584] gzip module has no custom exception

Changes by Sridhar Ratnakumar : -- versions: +Python 3.1, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue6584] gzip module has no custom exception

Changes by Amaury Forgeot d'Arc : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http