[issue6277] Add description of new syntax of with to 2.7 whatsnew document.

Raymond Hettinger added the comment: Thanks. BTW, other doc patches are always welcome. -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___

[issue6277] Add description of new syntax of with to 2.7 whatsnew document.

Vikram U Shenoy added the comment: I see. OK, so you want me to close this bug ? -- ___ Python tracker ___ ___ Python-bugs-list mailin

[issue3407] test_urllib2_localnet fails on MacOS X 10.4.11 (Intel)

Senthil added the comment: Closing it based on the (test pass) comments. Fix was applied in r67779, r6. -- status: open -> closed ___ Python tracker ___ _

[issue3672] Ill-formed surrogates not treated as errors during encoding/decoding

Changes by hippietrail : -- nosy: +hippietrail ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue6290] cPickle can misread data type

Alexandre Vassalotti added the comment: Could you provide a test case? The behaviour you are describing sounds like a bug in cPickle. -- nosy: +alexandre.vassalotti ___ Python tracker __

[issue6289] compile() raises SyntaxError with confusing message for some decoding problems

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

[issue6286] distutils upload command doesn't work with http proxy

Tarek Ziadé added the comment: done in r73436. Will merge it into 3.2 after 3.1 is tagged. I am leaving this issue open until the merge in 3.2 is done. -- ___ Python tracker ___

[issue6286] distutils upload command doesn't work with http proxy

Changes by Tarek Ziadé : -- type: -> feature request ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue6290] cPickle can misread data type

New submission from Alex James : When using cPickle to pickle / unpickle an object instance whose __dict__ contains a dictionary of NumPy Arrays (on a windows32 system), some of the array elements have the wrong type raising a ValueError: could not convert string to float. On UNIX platform thi

[issue6289] compile() raises SyntaxError with confusing message for some decoding problems

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

[issue6289] compile() raises SyntaxError with confusing message for some decoding problems

New submission from Jean-Paul Calderone : Consider this source file: # coding: ascii ☃ It is not a valid Python program (for several reasons). The first problem encountered is that bytes representing SNOWMAN do not fit into ASCII, so the file cannot be decoded using the declared encoding.

[issue5468] urlencode does not handle "bytes", and could easily handle alternate encodings

Miles Kaufmann added the comment: parse_qs and parse_qsl should also grow encoding and errors parameters to pass to the underlying unquote(). -- nosy: +milesck ___ Python tracker __

[issue6288] Update contextlib.nested docs in light of deprecation

New submission from Nick Coghlan : Just a placeholder to remind me to implement the suggestion from python-dev of updating the contextlib.nested docs to show: 1. The one remaining valid use case (variable number of context managers) 2. The warnings module incantation needed to suppress the depre

[issue6250] Python compiles dead code

Martin v. Löwis added the comment: I'm also happy with rejecting the patch, and agree with everything that has been brought up against it: from an end-user point of view, there is a negligible-if-any benefit (e.g. if you want to speed up importing, try to reduce the number of stat() calls instea

[issue6234] cgi.FieldStorage is broken when given POST data

Changes by Miles Kaufmann : -- nosy: +milesck ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue6250] Python compiles dead code

Raymond Hettinger added the comment: Martin, am transferring this to you for adjudication. I'm -0 on the patch. On the plus side, the code is well thought-out and reasonably well tested. On the minus side, it complexifies the compiler in a way that may make it more difficult to maintain. The

[issue6250] Python compiles dead code

James Abbatiello added the comment: Raymond, I've updated peephole.c to allow code to terminate with any of RETURN_VALUE, END_FINALLY or RAISE_VARARGS [0-3]. I also added tests to test_peepholer.py to make sure the peepholer still works in these cases. -- _

[issue6192] add disable_nagle_algorithm to SocketServer.TCPServer

Kristján Valur Jónsson added the comment: On consideration, it is more appropariate to have the disable_nagle_algorithm as part of StreamRequestHandler rather than in the TCPSockerServer. It then sits right next to the rfile and wfile that affect it. The RequestHandlers aren't documented as

[issue6287] distutils.core.setup does not document the 'license' meta-data

New submission from Matthew Smart : The 'license' meta-data option is not listed under: http://docs.python.org/distutils/setupscript.html#meta-data There are others, too, from: $ python setup.py --help .. snip .. Information display options (just display information, ignore any commands)  --he

[issue6250] Python compiles dead code

Raymond Hettinger added the comment: James, the peepholer currently assumes that codestrings terminate with RETURN_VALUE. Is this assumption invalidated by your code? -- ___ Python tracker

[issue6250] Python compiles dead code

James Abbatiello added the comment: I should add that the patch doesn't only address dead user-code. It also eliminates code that the compiler generates itself but that would be unreachable at runtime. Consider the following function: def foo(x): if x: raise Something else: raise

[issue6250] Python compiles dead code

Raymond Hettinger added the comment: Are you looking for dead code detection (like a lint utility) or automatic dead code removal (modified code)? -- ___ Python tracker ___ _

[issue6250] Python compiles dead code

Collin Winter added the comment: Standalone bytecode-modifying tools almost never check that they're outputting correct bytecode. http://code.activestate.com/recipes/277940/ makes no attempt to check what version of Python it's running under; running it under Unladen Swallow 2009Q1 would have pr

[issue6208] path separator output ignores shell's path separator: / instead of \

Eric Smith added the comment: Tim Golden wrote: > Just for information's sake, the shell APIs usually only accept backslashes. That's good to know. Do you have any specific examples? CreateFile and the like, which is where my experience is, take either. 90% of my Windows Python programs use s

[issue6208] path separator output ignores shell's path separator: / instead of \

Tim Golden added the comment: Eric Smith wrote: > Eric Smith added the comment: > >> So is this a cosmetic issue or a functional issue? > > It's a cosmetic issue. > >> Also, even if it could figure that out, how would it know whether >> a particular filename "stringification" with os.path.j

[issue6208] path separator output ignores shell's path separator: / instead of \

Eric Smith added the comment: > So is this a cosmetic issue or a functional issue? It's a cosmetic issue. > Also, even if it could figure that out, how would it know whether > a particular filename "stringification" with os.path.join() was > intended for display to the user or to be passed t

[issue6205] sdist doesn't include data_files

James added the comment: great, thanks for the info. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue5811] io.BufferedReader.peek(): Documentation differs from Implementation

Lucas Prado Melo added the comment: Ok A new patch without read1() changes. Only one test fails, a read1() test: == FAIL: test_read1 (test.test_io.PyBufferedRWPairTest) --

[issue5811] io.BufferedReader.peek(): Documentation differs from Implementation

Nick Coghlan added the comment: The doc revision definitely does a better job of characterising the current underspecified behaviour :) I agree with Antoine that "at most a single read" would be better wording. -- ___ Python tracker

[issue5811] io.BufferedReader.peek(): Documentation differs from Implementation

Antoine Pitrou added the comment: I haven't read the patch in detail but I don't think you should have changed read1(). read1() is there for optimization purposes and its current behaviour makes sense IMO. -- versions: +Python 2.7 ___ Python tracker

[issue6286] distutils upload command doesn't work with http proxy

New submission from Tarek Ziadé : upload is base on httplib and doesn't use the http_proxy envrionment variable. So it's impossible to upload a file behind a firewall. Let's change the command so it uses a proxy if set -- assignee: tarek components: Distutils messages: 89398 nosy: tarek

[issue6282] In tarfile, compression level cannot be specified

Omri Shaked added the comment: Silly me... Thanks! -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6250] Python compiles dead code

Raymond Hettinger added the comment: I'm curious to whether this needs to be embedded in the compiler or whether a standalone tool can be offered. See http://code.activestate.com/recipes/277940/ for an example of processing the bytecodes directly. FWIW, deadcode can already be detected by some

[issue6278] http.server, BaseHTTPRequestHandler write string error

Amaury Forgeot d'Arc added the comment: the HTTP response should be a bytes string: self.wfile.write(b'test') -- nosy: +amaury.forgeotdarc resolution: -> invalid status: open -> closed ___ Python tracker _