multiple 2.7.3 versions?

Robin Becker robin at
Fri Feb 15 11:53:22 CET 2013

A colleague reports that this python from a recent Ubuntu x86_x64

Python 2.7.3 (default, Sep 26 2012, 21:51:14)

contains a fix of this bug

however, all of my other Python 2.7.3s seem to lack this 'fix'.

I would have thought that for a fix to appear in python we should at least get a 
micro version change, but the text here

> The developers issue “bugfix” releases of older versions, so the stability of existing releases gradually improves. Bugfix releases, indicated by a third component of the version number (e.g. 2.5.3, 2.6.2), are managed for stability; only fixes for known problems are included in a bugfix release, and it’s guaranteed that interfaces will remain the same throughout a series of bugfix releases.

would seem to indicate that changes to the spelling of a public variable would 
not change even with a change to the micro level so my colleague's machine 
should not produce this output

>>>> from compiler import consts
>>>> dir(consts)
> '__builtins__', '__doc__', '__file__', '__name__', '__package__']

where the originally mis-spelled SC_GLOBAL_EXPLICT has changed to 

Can someone explain how this 'fix' is leaking out onto his machine? On all the 
other machines I have access to I'm seeing something similar to this
> C:\tmp>python
> Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)] on win32
> Type "help", "copyright", "credits" or "license" for more information.
>>>> from compiler import consts
>>>> dir(consts)
Robin Becker

More information about the Python-list mailing list