Path: csiph.com!usenet.pasdenom.info!dedibox.gegeweb.org!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!nerim.net!novso.com!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'win32': 0.03; 'skip:[ 20': 0.03; 'output': 0.04; 'compiler': 0.05; 'fixes': 0.05; 'versions,': 0.05; 'indicated': 0.07; 'python': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'release,': 0.09; 'sep': 0.09; 'spelling': 0.09; 'bug': 0.10; 'component': 0.15; 'interfaces': 0.15; "'__doc__',": 0.16; "'__file__',": 0.16; '2.7.3': 0.16; 'machine?': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'subject:2.7.3': 0.16; 'subject:versions': 0.16; 'url:faq': 0.16; 'url:general': 0.16; 'fix': 0.17; 'variable': 0.20; 'changes': 0.20; 'bit': 0.21; 'import': 0.21; 'originally': 0.23; 'url:bugs': 0.24; 'machine': 0.24; 'least': 0.25; 'header:User-Agent:1': 0.26; 'developers': 0.26; 'appear': 0.26; '(e.g.': 0.27; 'older': 0.27; 'change,': 0.27; 'header:X-Complaints-To:1': 0.28; '>>>>': 0.29; 'releases,': 0.29; 'included': 0.29; "i'm": 0.29; "skip:' 10": 0.30; 'url:python': 0.32; "skip:' 20": 0.32; 'ubuntu': 0.33; 'to:addr :python-list': 0.33; 'version': 0.34; 'changed': 0.34; 'text': 0.34; 'third': 0.34; 'machines': 0.35; 'subject:?': 0.35; 'similar': 0.35; 'something': 0.35; 'received:org': 0.36; 'explain': 0.36; 'but': 0.36; 'url:org': 0.36; 'should': 0.36; 'problems': 0.36; 'level': 0.37; 'throughout': 0.37; 'url:docs': 0.38; 'to:addr:python.org': 0.39; 'where': 0.40; 'header:Received:5': 0.40; 'series': 0.63; 'more': 0.63; 'here': 0.65; 'charset:windows-1252': 0.65; 'lack': 0.71; 'received:109': 0.74; 'guaranteed': 0.76; 'it\x92s': 0.84; 'colleague': 0.91; 'releases.': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Robin Becker Subject: multiple 2.7.3 versions? Date: Fri, 15 Feb 2013 10:53:22 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Gmane-NNTP-Posting-Host: 109.174.168.73 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 46 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1360925614 news.xs4all.nl 6983 [2001:888:2000:d::a6]:49121 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:38913 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