strange results from sys.version

Sridhar Ratnakumar sridharr at
Tue Sep 28 01:36:01 CEST 2010

On 2010-09-27, at 4:30 PM, Robert Kern wrote:

> On 9/27/10 6:01 PM, John Machin wrote:
>> I am trying to help a user of my xlrd package who says he is getting anomalous
>> results on his "work computer" but not on his "home computer".
>> Attempts to reproduce his alleged problem in a verifiable manner on his "work
>> computer" have failed, so far ... the only meaning difference in script output
>> is in sys.version
>> User (work): sys.version: 2.7 (r27:82500, Aug 23 2010, 17:18:21) etc
>> Me : sys.version: 2.7 (r27:82525, Jul 4 2010, 09:01:59) etc
>> I have just now downloaded the Windows x86 msi from and
>> reinstalled it on another computer. It gives the same result as on my primary
>> computer (above).
>> User result looks whacked: lower patch number, later date. says
>> "Python 2.7 was released on July 3rd, 2010."
>> Is it possible that the "work computer" is using an unofficial release? What
>> other possibilities are there?
> ActivePython was released on Aug 25:


If it is ActivePython, the first line of the interactive shell (in credits section) should print something like:

  ActivePython (ActiveState Software Inc.) 

Also what is the output of "python -m activestate"?


More information about the Python-list mailing list