king kikapu wrote: > On Apr 19, 12:10 pm, Ant <[EMAIL PROTECTED]> wrote: >>> 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 +44 150 684 7255 +1 800 494 3119 Holden Web LLC/Ltd http://www.holdenweb.com Skype: holdenweb http://del.icio.us/steve.holden Recent Ramblings http://holdenweb.blogspot.com -- http://mail.python.org/mailman/listinfo/python-list
