Mailman 3 August 2010 - Python-Dev

Python 2.6.6 release candidate 1 now available
by Barry Warsaw 04 Aug '10

04 Aug '10

Hello fellow Pythoneers and Pythonistas, The source tarballs and Windows installers for the first (and hopefully only) Python 2.6.6 release candidate is now available: http://www.python.org/download/releases/2.6.6/ As usual, we would love it if you could download, install, and test these with your favorite projects and environments. A truly impressive number of bug have been fixed since Python 2.6.5, with the full NEWS file available here: http://www.python.org/download/releases/2.6.6/NEWS.txt Barring complications, we expect to release Python 2.6.6 final on August 16, 2010. Please note that with the release of Python 2.7 final on July 3, 2010, and in accordance with Python policy, Python 2.6.6 is the last scheduled bug fix maintenance release of the 2.6 series. Because of this, your testing of this release candidate will help immensely. We will of course continue to support security fixes in Python 2.6 for quite some time. My thanks go out to everyone who has helped contribute fixes great and small, and much testing and bug tracker gardening for Python 2.6.6. The excellent folks on #python-dev are true Pythonic heros too. Enjoy, -Barry (on behalf of the Python development community)

1 0

question
by Sarah Hasanlo Nikfar 04 Aug '10

04 Aug '10

hi i face with problem when i run one sample on cygwin: please help me Exception happened during processing of request from ('127.0.0.1', 49154) Traceback (most recent call last): File "/usr/local/lib/python2.5/SocketServer.py", line 222, in handle_request self.process_request(request, client_address) File "/usr/local/lib/python2.5/SocketServer.py", line 241, in process_request self.finish_request(request, client_address) File "/usr/local/lib/python2.5/SocketServer.py", line 254, in finish_request self.RequestHandlerClass(request, client_address, self) File "/usr/local/lib/python2.5/SocketServer.py", line 522, in __init__ self.handle() File "/usr/local/lib/python2.5/BaseHTTPServer.py", line 316, in handle self.handle_one_request() File "/usr/local/lib/python2.5/BaseHTTPServer.py", line 310, in handle_one_req uest method() File "/usr/local/lib/python2.5/SimpleHTTPServer.py", line 46, in do_GET self.copyfile(f, self.wfile) File "/usr/local/lib/python2.5/SimpleHTTPServer.py", line 175, in copyfile shutil.copyfileobj(source, outputfile) File "/usr/local/lib/python2.5/shutil.py", line 29, in copyfileobj fdst.write(buf) File "/usr/local/lib/python2.5/socket.py", line 274, in write self.flush() File "/usr/local/lib/python2.5/socket.py", line 261, in flush self._sock.sendall(buffer) error: (113, 'Software caused connection abort')

3 2

pickle output not unique
by Kristján Valur Jónsson 04 Aug '10

04 Aug '10

Hi there. I was made aware of this oddity here: import cPickle reffed = "xKITTENSx"[1:-1] print repr(cPickle.dumps(reffed)) print repr(cPickle.dumps("xKITTENSx"[1:-1])) These strings are different, presumably because of the (ob_refcnt == 1) optimization used during object pickling. This might come as a suprise to many, and is potentially dangerous if pickling is being used as precursor to some hashing function. For example, we use code that caches function calls, using something akin to: myhash = hash(cPickle.dumps(arguments)) try: cached_args, cached_value = cache[myhash] if cached_args == arguments: return cached_value except KeyError: value = Function(*args) cache[myhash] = artuments, value return value The non-uniqueness of the pickle string will cause unnecessary cache misses in this code. Pickling is useful as a precusor because it allows for more varied object types than hash() alone would. I just wanted to point this out. We'll attempt some local workarounds here, but it should otherwise be simple to modify pickling to optionally turn off this optimization and always generate the same output irrespective of the internal reference counts of the objects. Cheers, Kristján

3 5

Re: [Python-Dev] [Python-checkins] r83704 - in python/branches/release26-maint: Lib/asyncore.py Misc/ACKS Misc/NEWS
by Barry Warsaw 04 Aug '10

04 Aug '10

Hi Giampaolo, Now that we're in quasi-freeze for 2.6.6 final, this is the kind of change I'd like to review before backporting. In this case, I'll let it through, but please check with me first next time. And thanks for your work! -Barry On Aug 04, 2010, at 10:58 AM, giampaolo.rodola wrote: >Author: giampaolo.rodola >Date: Wed Aug 4 10:58:38 2010 >New Revision: 83704 > >Log: >Merged revisions 83703 via svnmerge from >svn+ssh://pythondev@svn.python.org/python/branches/release27-maint > >........ > r83703 | giampaolo.rodola | 2010-08-04 10:35:25 +0200 (mer, 04 ago > 2010) | 1 line > fix issue #2944: asyncore doesn't handle connection refused > correctly (patch by Alexander Shigin) >........ > > >Modified: > python/branches/release26-maint/ (props changed) > python/branches/release26-maint/Lib/asyncore.py > python/branches/release26-maint/Misc/ACKS > python/branches/release26-maint/Misc/NEWS > >Modified: python/branches/release26-maint/Lib/asyncore.py >============================================================================== >--- python/branches/release26-maint/Lib/asyncore.py (original) >+++ python/branches/release26-maint/Lib/asyncore.py Wed Aug 4 >10:58:38 2010 @@ -422,8 +422,11 @@ > self.handle_read() > > def handle_connect_event(self): >- self.connected = True >+ err = self.socket.getsockopt(socket.SOL_SOCKET, >socket.SO_ERROR) >+ if err != 0: >+ raise socket.error(err, _strerror(err)) > self.handle_connect() >+ self.connected = True > > def handle_write_event(self): > if self.accepting: > >Modified: python/branches/release26-maint/Misc/ACKS >============================================================================== >--- python/branches/release26-maint/Misc/ACKS (original) >+++ python/branches/release26-maint/Misc/ACKS Wed Aug 4 >10:58:38 2010 @@ -817,3 +817,4 @@ > Peter Åstrand > Jesse Noller > Fredrik Håård >+Alexander Shigin > >Modified: python/branches/release26-maint/Misc/NEWS >============================================================================== >--- python/branches/release26-maint/Misc/NEWS (original) >+++ python/branches/release26-maint/Misc/NEWS Wed Aug 4 >10:58:38 2010 @@ -89,6 +89,8 @@ > Library > ------- > >+- Issue #2944: asyncore doesn't handle connection refused correctly. >+ > - Issue #8447: Make distutils.sysconfig follow symlinks in the path to > the interpreter executable. This fixes a failure of > test_httpservers on OS X.

1 0

(no subject)
by Sarah Hasanlo Nikfar 04 Aug '10

04 Aug '10

1 0

Windows MSI installer with minimal options
by Paul Kippes 04 Aug '10

04 Aug '10

Martin, For the most part, the information at http://www.python.org/download/releases/2.4/msi/ assisted me with automating a 2.7 installation on Windows XP. The following initial attempt, however, failed to provide a working python installation. (Messages are either "The system cannot execute the specified program." or "This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.") msiexec /qb /i python-2.7.msi ALLUSERS=1 ADDLOCAL=Extensions After looking through Tools/msi/msi.py, I was able to automate a minimal and working Python installation with this adjustment: ADDLOCAL=Extensions,SharedCRT Since the only reference I could find to the above web page was when the MSI installer was first announced (http://www.python.org/download/releases/2.4.2), the installer options may have changed since then. Would you check if my change is what you intended and perhaps migrate the web page of the 2.4 release note to 2.7? Thanks!

1 0

Status of Lib/_threading_local.py ?
by Antoine Pitrou 04 Aug '10

04 Aug '10

Hello, While Lib/_threading_local.py is meant as a fallback Python implementation of thread-local objects, it looks like it will never be invoked in practice. The reason is that the thread-local code in Modules/_threadmodule.c in unconditionally compiled. Furthermore, _threading_local.py imports threading which itself imports _thread, so it's not possible for _threading_local to function if for some reason _thread fails to build or import. What should we do with _threading_local? Keep it as an example of a Python implementation (which is vastly slower than what a C implementation can do and also currently less robust), or plainly remove it? Regards Antoine.

1 0

co_firstlineno on decorated functions
by Eli Bendersky 03 Aug '10

03 Aug '10

[Since I received no replies on this in python-list, perhaps python-dev is more appropriate] Hello, I've been tinkering with __code__.co_firstlineno for testing the trace.py module (Python Issue 9315), and ran into an interesting problem. Consider this code: def dummydecorator(f): return f def foo(a): return a @dummydecorator def bar(a): return a if __name__ == "__main__": print foo.__code__.co_firstlineno print bar.__code__.co_firstlineno ---- The first print out correctly specifies the line "def foo" is in. However, the second one points to the line with "@dummydecorator" instead of "def bar". [Python 2.6] The side-effects of this behavior can be easily seen in the output of modules like trace and profile. Would you say it's normal, or could this be considered a bug? Eli

8 9

Tracker status
by Nick Coghlan 03 Aug '10

03 Aug '10

Are the bug tracker and meta-tracker down for anyone else, or is it just me? Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

10 11

breaking an exception chain
by R. David Murray 03 Aug '10

03 Aug '10

Working with Catherine on an argparse bug, we ran into a test that was apparently failing by raising a SystemExit, when the test harness was supposed to be catching that error. It took us a bit to realize that there wasn't really a SystemExit error, but that what we were seeing was the SystemExit chained to the exception the test harness was purposfully raising after catching the SystemExit. In Python2, only the second, intentionally raised exception would be printed by unittest. In Python3, the "main error" printed by unittest is the SystemExit, and the error raised by the test harness appears after the "while processing the above error" sentence. Needless to say, this is a bit confusing. So I thought I'd break the exception chain before raising the error the test harness really wants to raise. However, I can't figure out any way to do that. Am I missing something, or this a missing feature? -- R. David Murray www.bitdance.com

2 2