[Python-Dev] version of freshly built 2.7 python

[Ethan Furman]

On 04/02, Brian Curtin wrote:
> On Thu, Apr 2, 2015 at 10:19 PM, Ethan Furman <ethan at stoneleaf.us> wrote:
>> On 04/02, Alexander Walters wrote:
>>> On 4/2/2015 21:29, Ethan Furman wrote:
>>>>
>>>> I just built the latest version of Python 2.7 on my development machine -- or so I thought.  When I invoke it, I get:
>>>>
>>>>    Python 2.7.6+ (2.7:1beb3e0507fa, Apr  2 2015, 17:57:53)
>>>>
>>>> Why am I not seeing 2.7.9?
>>>
>>> Are you building from mercurial or a source tarball?
>>
>> Mercurial:
>>
>>   ethan at code:~/source/python/python2.7$ hg parent
>>   changeset:   90450:1beb3e0507fa
>>   branch:      2.7
>>   parent:      90434:b428b803f71f
>>   user:        Zachary Ware <zachary.ware at gmail.com>
>>   date:        Thu Apr 24 13:20:27 2014 -0500
>>   files:       Lib/test/test_itertools.py
>>   description:
>>   Issue #21346: Fix typos in test_itertools.  Patch by Brian Kearns.
> 
> That's almost a year old. Update it?

A fresh pull only garnared 13 new commits, and an hg update in the 2.7 directory changed nothing.

I even tried updating to default, then back to 2.7, but I get the same parent.  hg branches shows

default                    90453:d84a69b7ba72
2.7                        90450:1beb3e0507fa
3.1                        90264:c7b93519807a
2.6                        90100:23a60d89dbd4
3.4                        90451:901b9afc918e (inactive)
3.3                        90266:a8445ead2f9e (inactive)
3.2                        90265:0a7d4cdc4c8d (inactive)

hmmm... those numbers are about 5000 off!  Okay, deleting and recloning...

Okay, the revisions are matching up now -- don't know what happened, but nothing a simple nuke couldn't solve!

Now-wondering-if-I-ever-did-an-hg-pull'ly yrs,
~Ethan~