Upgrade Python 2.6.4 to 2.6.5

[Werner F. Bruhin]

Just upgraded on my Windows 7 machine my copy of 2.6.4 to 2.6.5.

However doing sys.version still shows 2.6.4 even so python.exe is dated
19. March 2010 with a size of 26.624 bytes.

Is this a known issue? Or did I do something wrong?

If I install to a new folder all is well, but I would have to install
all my other stuff again (kinterbasdb, matplotlib, sphinx etc etc).

Werner

 

[Martin v. Loewis]

Just upgraded on my Windows 7 machine my copy of 2.6.4 to 2.6.5.

However doing sys.version still shows 2.6.4 even so python.exe is dated
19. March 2010 with a size of 26.624 bytes.

Is this a known issue? Or did I do something wrong?

Look at the copy of python26.dll. This should be the new one; perhaps
you have another copy in the system32 folder?

Did the upgrade inform you that it was an upgrade, or did it warn you
that you would overwrite the previous installation?

Regards,
Martin

 

[Martin v. Loewis]

Just upgraded on my Windows 7 machine my copy of 2.6.4 to 2.6.5.

However doing sys.version still shows 2.6.4 even so python.exe is dated
19. March 2010 with a size of 26.624 bytes.

Is this a known issue? Or did I do something wrong?

Look at the copy of python26.dll. This should be the new one; perhaps
you have another copy in the system32 folder?

Did the upgrade inform you that it was an upgrade, or did it warn you
that you would overwrite the previous installation?

Regards,
Martin

 

[Werner F. Bruhin]

Martin,

Thanks for the quick reply.

Look at the copy of python26.dll. This should be the new one; perhaps
you have another copy in the system32 folder?

The one in system32 is 2.6.5 and the one in c:\python26 is 2.6.4.

When will it install into system32?

Did the upgrade inform you that it was an upgrade, or did it warn you
that you would overwrite the previous installation?

It warned me that there is a previous installation.

Best regards
Werner

 

[Martin v. Loewis]

When will it install into system32?

When you install "for all users".

It warned me that there is a previous installation.

Hmm. You don't remember the exact message, do you?
I guess it was a popup saying "[TARGETDIR] exists. Are you sure you want
to overwrite existing files?", and that it was not
a red text saying "This update will replace your existing [ProductLine]
installation."

Please confirm.

If so, you now have two Python installations in the same location; one
for all users, and the older one just for you (or vice versa).

I recommend to uninstall them both, and start over.

Regards,
Martin

 

[python]

Martin,

If we install over an existing version of Python 2.6.5, will our PTH
files and site-packages be preserved?

Or do we need to back out our 3rd party packages, install Python 2.6.5
and then manually restore our 3rd party packages?

Thank you,
Malcolm

 

[Terry Reedy]

Martin,

If we install over an existing version of Python 2.6.5, will our PTH
files and site-packages be preserved?

Or do we need to back out our 3rd party packages, install Python 2.6.5
and then manually restore our 3rd party packages?

In my experience on WinXP, installing x.y.z+1 over x.y.z nicely leaves
sitepackages alone as well as any other directories I have added under
the pythonxy directory. An uninstall and reinstall should also leave
user stuff alone.

Installing x.y+1 create and install in a new pythonx<y+1> directory,
leaving one to copy from pythonxy subdirs as desired.

It appears that the OP confused things by switching between one and all
user installs.

Terry Jan Reedy

 

[Martin v. Löwis]

If we install over an existing version of Python 2.6.5, will our PTH

files and site-packages be preserved?

Or do we need to back out our 3rd party packages, install Python 2.6.5
and then manually restore our 3rd party packages?

An upgrade installation will only replace the Python files, and leave
all other files alone.

Regards,
Martin

 

[Werner F. Bruhin]

When will it install into system32?

When you install "for all users".

It warned me that there is a previous installation.

Hmm. You don't remember the exact message, do you?
I guess it was a popup saying "[TARGETDIR] exists. Are you sure you want
to overwrite existing files?", and that it was not
a red text saying "This update will replace your existing [ProductLine]
installation."

Please confirm.
Correct that was it.
If so, you now have two Python installations in the same location; one
for all users, and the older one just for you (or vice versa).

Yes, that is what I did ages ago.

I recommend to uninstall them both, and start over.

O.K., will do that.

Thanks for your help
Werner

 

[Michel Claveau - MVP]

Hi!

If you are under Vista, or Windows 7, have you unactivate UAC, before
the update?

@+

MCI