About installing new Python version.

[king kikapu]

Hi to all,

i started with Python at v2.5 and now i see that a new version is
released.
As i already have a lot of stuff for Python installed in the site-
packages directory, which is the correct way to install a new Python
version without do any damage ?

Remove Python and ALL Python related software and install them all
over again (painful)?
Remove Python and do not touch anything else and install new version
on top of them at the same directory ?
Any other choice available ?

Thanks a lot for any help!

[half.italian]

On Apr 19, 2:03 am, king kikapu <[e-mail]:

Hi to all,

i started with Python at v2.5 and now i see that a new version is
released.
As i already have a lot of stuff for Python installed in the site-
packages directory, which is the correct way to install a new Python
version without do any damage ?

Remove Python and ALL Python related software and install them all
over again (painful)?
Remove Python and do not touch anything else and install new version
on top of them at the same directory ?
Any other choice available ?

Thanks a lot for any help!

Just install the new version. It should link everything back up so the
new version is active, but the old versions are intact.

~Sean

[king kikapu]

On Apr 19, 11:39 am, [e-mail] wrote:

On Apr 19, 2:03 am, king kikapu <[e-mail]:

Hi to all,

i started with Python at v2.5 and now i see that a new version is
released.
As i already have a lot of stuff for Python installed in the site-
packages directory, which is the correct way to install a new Python
version without do any damage ?

Remove Python and ALL Python related software and install them all
over again (painful)?
Remove Python and do not touch anything else and install new version
on top of them at the same directory ?
Any other choice available ?

Thanks a lot for any help!

Just install the new version. It should link everything back up so the
new version is active, but the old versions are intact.

~Sean

I installed 2.5.1 and as the installer said, it have replaced my old
installation with the new one, something like i wanted to do! So i
checked and everything seems to working fine. But this is an update
release to 2.5, i do not know what is happening when, for example, a
totally new Python version come out, like 2.6 or 2.7 or...

[Ant]

checked and everything seems to working fine. But this is an update

release to 2.5, i do not know what is happening when, for example, a
totally new Python version come out, like 2.6 or 2.7 or...

Again just install it - it will by default install alongside Python
2.5 in a different directory, and set itself as the default python
version. You'll then need to update all your third party extensions to
ones compiled against the new version - so if you have a lot of these,
it makes sense to wait a while before upgrading.

--
Ant.

[king kikapu]

On Apr 19, 12:10 pm, Ant <[e-mail]:

checked and everything seems to working fine. But this is an update
release to 2.5, i do not know what is happening when, for example, a
totally new Python version come out, like 2.6 or 2.7 or...

Again just install it - it will by default install alongside Python
2.5 in a different directory, and set itself as the default python
version. You'll then need to update all your third party extensions to
ones compiled against the new version - so if you have a lot of these,
it makes sense to wait a while before upgrading.

--
Ant.

Hmm...ok, i was sure that i wouldn't avoid that...The nice thing is
that 2.5.1 installed in default directory so no problem for now.
Thanks!

[Steve Holden]

king kikapu wrote:

On Apr 19, 12:10 pm, Ant <[e-mail]:

>>checked and everything seems to working fine. But this is an update
release to 2.5, i do not know what is happening when, for example, a
totally new Python version come out, like 2.6 or 2.7 or...

Again just install it - it will by default install alongside Python
2.5 in a different directory, and set itself as the default python
version. You'll then need to update all your third party extensions to
ones compiled against the new version - so if you have a lot of these,
it makes sense to wait a while before upgrading.

--
Ant.

Hmm...ok, i was sure that i wouldn't avoid that...The nice thing is
that 2.5.1 installed in default directory so no problem for now.
Thanks!

Good question. kk is right - with a change in *major* version (such as
2.4 to 3.5, 3.5 to 3.6) the compiled extensions will be incompatible,
and will need to be recompiled. This can take a while, as extension
authors frequently have other things to do besides maintain their
extensions.

As you have found out, though, when only the *minor* version changes you
can just frop the new version in over the old and all your installed
extensions and packages continue to work just fine.

regards
Steve
--
Steve Holden [phone] [phone]
Holden Web LLC/Ltd http://www.holdenweb.com
Skype: holdenweb http://del.icio.us/steve.holden
Recent Ramblings http://holdenweb.blogspot.com

[king kikapu]

On Apr 19, 1:51 pm, Steve Holden <[e-mail]:

Good question. kk is right - with a change in *major* version (such as
2.4 to 3.5, 3.5 to 3.6) the compiled extensions will be incompatible,
and will need to be recompiled. This can take a while, as extension
authors frequently have other things to do besides maintain their
extensions.

As you have found out, though, when only the *minor* version changes you
can just frop the new version in over the old and all your installed
extensions and packages continue to work just fine.

regards
Steve
--
Steve Holden [phone] [phone]
Holden Web LLC/Ltd http://www.holdenweb.com
Skype: holdenweb http://del.icio.us/steve.holden
Recent Ramblings http://holdenweb.blogspot.com

Thanks Steve, it is just the way i understood this, after seeing what
the installer did.