multiple 2.7.3 versions?

From	Robin Becker <robin@reportlab.com>
Subject	multiple 2.7.3 versions?
Date	2013-02-15 10:53 +0000
Newsgroups	comp.lang.python
Message-ID	<mailman.1801.1360925614.2939.python-list@python.org> (permalink)

Show all headers | View raw

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

http://bugs.python.org/issue15212

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

http://docs.python.org/2/faq/general.html#how-stable-is-python

> 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)
> ['CO_FUTURE_ABSIMPORT', 'CO_FUTURE_DIVISION', 'CO_FUTURE_PRINT_FUNCTION',
> 'CO_FUTURE_WITH_STATEMENT', 'CO_GENERATOR', 'CO_GENERATOR_ALLOWED',
> 'CO_NESTED', 'CO_NEWLOCALS', 'CO_OPTIMIZED', 'CO_VARARGS', 'CO_VARKEYWORDS',
> 'OP_APPLY', 'OP_ASSIGN', 'OP_DELETE', 'SC_CELL', 'SC_FREE',
> 'SC_GLOBAL_EXPLICIT', 'SC_GLOBAL_IMPLICIT', 'SC_LOCAL', 'SC_UNKNOWN',
> '__builtins__', '__doc__', '__file__', '__name__', '__package__']

where the originally mis-spelled SC_GLOBAL_EXPLICT has changed to 
SC_GLOBAL_EXPLICIT.

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)
> ['CO_FUTURE_ABSIMPORT', 'CO_FUTURE_DIVISION', 'CO_FUTURE_PRINT_FUNCTION', 'CO_FUTURE_WITH_STATEMENT', 'CO_GENERATOR', 'CO_GENERATOR_ALLOWED', 'CO_NESTED', 'CO_NEWLOCALS', 'CO_OPTIMIZED', 'CO_VARARGS', 'CO_VARKEYWORDS', 'OP_APPLY', 'OP_ASSIGN', 'OP_DELETE', 'SC_CELL', 'SC_FREE', 'SC_GLOBAL_EXPLICT', 'SC_GLOBAL_IMPLICIT', 'SC_LOCAL', 'SC_UNKNOWN', '__builtins__', '__doc__', '__file__', '__name__', '__package__']
>>>>
-- 
Robin Becker

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

multiple 2.7.3 versions? Robin Becker <robin@reportlab.com> - 2013-02-15 10:53 +0000
  Re: multiple 2.7.3 versions? Roy Smith <roy@panix.com> - 2013-02-15 09:00 -0500
    Re: multiple 2.7.3 versions? Robin Becker <robin@reportlab.com> - 2013-02-15 14:33 +0000
    Re: multiple 2.7.3 versions? Ned Deily <nad@acm.org> - 2013-02-15 14:17 -0800
  Re: multiple 2.7.3 versions? Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-02-16 01:24 +1100

csiph-web