installing 2.4

[David Bolen]

Re: installing 2.4

"Jive" <someone@micros oft.com> writes:
[color=blue]
> It's only getting worse. I went to Add/remove programs and removed 2.4.
> Now Python 2.4 numarray and Python 2.4 pywin extensions are still listed as
> installed, but I cannot remove them.[/color]

You mentioned in your first post about "copying your site package"
.... did you actually make a copy or did you perhaps "move" your
site-packages directory from beneath 2.3 to under 2.4. If so, then
the uninstall entry in the registry is not going to find the files to
be able to uninstall them.

Worst case you should be able to reinstall Python 2.3, and your
extension packages from their installer images. Don't worry about the
uninstall list in Add/Remove programs as reinstalling the packages
will just update their entries. That will refresh the files in your
Python 2.3 tree, and providing you don't disable the option, should
re-establish file associations and what not back to a 2.3
installation.

-- David

[David Bolen]

Re: installing 2.4

"Jive" <someone@micros oft.com> writes:
[color=blue]
> It's only getting worse. I went to Add/remove programs and removed 2.4.
> Now Python 2.4 numarray and Python 2.4 pywin extensions are still listed as
> installed, but I cannot remove them.[/color]

You mentioned in your first post about "copying your site package"
.... did you actually make a copy or did you perhaps "move" your
site-packages directory from beneath 2.3 to under 2.4. If so, then
the uninstall entry in the registry is not going to find the files to
be able to uninstall them.

Worst case you should be able to reinstall Python 2.3, and your
extension packages from their installer images. Don't worry about the
uninstall list in Add/Remove programs as reinstalling the packages
will just update their entries. That will refresh the files in your
Python 2.3 tree, and providing you don't disable the option, should
re-establish file associations and what not back to a 2.3
installation.

-- David

[Jive]

Re: installing 2.4


"Jeff Shannon" <jeff@ccvcorp.c om> wrote in message
news:10qvl42e44 q2177@corp.supe rnews.com...[color=blue]
> Jive wrote:
>[color=green]
> >As for checking the "applicatio n path", I don't know what that means.
> >
> >[/color]
>
> Go to a command prompt, and type 'echo %path%'. You'll see a list of
> all the directories that Windows looks in to find an executable -- i.e.,
> if you type 'python', Windows will work through this list of directories
> looking for a program named 'python', and will execute the first one it
> finds. If you want 2.3 to be your default Python version, then you
> should have 'C:\Python23\.' somewhere near the front of this list. If
> 'C:\Python24\.' is first in the list, then you may be running the wrong
> version of Python.[/color]

It now has Python22 in the path! How do I change that? I just now
re-installed 2.3 BTW.

[Jive]

Re: installing 2.4


"Jeff Shannon" <jeff@ccvcorp.c om> wrote in message
news:10qvl42e44 q2177@corp.supe rnews.com...[color=blue]
> Jive wrote:
>[color=green]
> >As for checking the "applicatio n path", I don't know what that means.
> >
> >[/color]
>
> Go to a command prompt, and type 'echo %path%'. You'll see a list of
> all the directories that Windows looks in to find an executable -- i.e.,
> if you type 'python', Windows will work through this list of directories
> looking for a program named 'python', and will execute the first one it
> finds. If you want 2.3 to be your default Python version, then you
> should have 'C:\Python23\.' somewhere near the front of this list. If
> 'C:\Python24\.' is first in the list, then you may be running the wrong
> version of Python.[/color]

It now has Python22 in the path! How do I change that? I just now
re-installed 2.3 BTW.

[Jive]

Re: installing 2.4


"David Bolen" <db3l@fitlinxx. com> wrote in message
news:uwtw0jdaf. fsf@fitlinxx.co m...[color=blue]
> "Jive" <someone@micros oft.com> writes:
>[color=green]
> > It's only getting worse. I went to Add/remove programs and removed 2.4.
> > Now Python 2.4 numarray and Python 2.4 pywin extensions are still listed[/color][/color]
as[color=blue][color=green]
> > installed, but I cannot remove them.[/color]
>
> You mentioned in your first post about "copying your site package"
> ... did you actually make a copy or did you perhaps "move" your
> site-packages directory from beneath 2.3 to under 2.4. If so, then
> the uninstall entry in the registry is not going to find the files to
> be able to uninstall them.[/color]

I copied, not moved;
[color=blue]
>
> Worst case you should be able to reinstall Python 2.3, and your
> extension packages from their installer images. Don't worry about the
> uninstall list in Add/Remove programs as reinstalling the packages
> will just update their entries. That will refresh the files in your
> Python 2.3 tree, and providing you don't disable the option, should
> re-establish file associations and what not back to a 2.3
> installation.
>[/color]

I've re-installed it, but things are all screwed up still.

[Jive]

Re: installing 2.4


"David Bolen" <db3l@fitlinxx. com> wrote in message
news:uwtw0jdaf. fsf@fitlinxx.co m...[color=blue]
> "Jive" <someone@micros oft.com> writes:
>[color=green]
> > It's only getting worse. I went to Add/remove programs and removed 2.4.
> > Now Python 2.4 numarray and Python 2.4 pywin extensions are still listed[/color][/color]
as[color=blue][color=green]
> > installed, but I cannot remove them.[/color]
>
> You mentioned in your first post about "copying your site package"
> ... did you actually make a copy or did you perhaps "move" your
> site-packages directory from beneath 2.3 to under 2.4. If so, then
> the uninstall entry in the registry is not going to find the files to
> be able to uninstall them.[/color]

I copied, not moved;
[color=blue]
>
> Worst case you should be able to reinstall Python 2.3, and your
> extension packages from their installer images. Don't worry about the
> uninstall list in Add/Remove programs as reinstalling the packages
> will just update their entries. That will refresh the files in your
> Python 2.3 tree, and providing you don't disable the option, should
> re-establish file associations and what not back to a 2.3
> installation.
>[/color]

I've re-installed it, but things are all screwed up still.

[Matt Gerrans]

Re: installing 2.4

"Peter Hansen" <peter@engcorp. com> wrote:[color=blue]
> Only pure Python code can run without change on a newer interpreter.[/color]

Is the interpreter smart enough to rebuild a pyc (if the corresponding py
file is there of course) file that was built by a previous version?

[Matt Gerrans]

Re: installing 2.4

"Peter Hansen" <peter@engcorp. com> wrote:[color=blue]
> Only pure Python code can run without change on a newer interpreter.[/color]

Is the interpreter smart enough to rebuild a pyc (if the corresponding py
file is there of course) file that was built by a previous version?

[Peter Hansen]

Re: installing 2.4

Matt Gerrans wrote:[color=blue]
> "Peter Hansen" <peter@engcorp. com> wrote:
>[color=green]
>>Only pure Python code can run without change on a newer interpreter.[/color]
>
> Is the interpreter smart enough to rebuild a pyc (if the corresponding py
> file is there of course) file that was built by a previous version?[/color]

Yes. The .pyc files contain a magic cookie that is
different in each major version, so 2.4 will recompile
your 2.3 .pyc files. .pyc files are not portable
between versions, generally, excepting maintenance releases.

-Peter

[Peter Hansen]

Re: installing 2.4

Matt Gerrans wrote:[color=blue]
> "Peter Hansen" <peter@engcorp. com> wrote:
>[color=green]
>>Only pure Python code can run without change on a newer interpreter.[/color]
>
> Is the interpreter smart enough to rebuild a pyc (if the corresponding py
> file is there of course) file that was built by a previous version?[/color]

Yes. The .pyc files contain a magic cookie that is
different in each major version, so 2.4 will recompile
your 2.3 .pyc files. .pyc files are not portable
between versions, generally, excepting maintenance releases.

-Peter

[Steve Holden]

Re: installing 2.4

Peter Hansen wrote:
[color=blue]
> Matt Gerrans wrote:
>[color=green]
>> "Peter Hansen" <peter@engcorp. com> wrote:
>>[color=darkred]
>>> Only pure Python code can run without change on a newer interpreter.[/color]
>>
>>
>> Is the interpreter smart enough to rebuild a pyc (if the corresponding
>> py file is there of course) file that was built by a previous version?[/color]
>
>
> Yes. The .pyc files contain a magic cookie that is
> different in each major version, so 2.4 will recompile
> your 2.3 .pyc files. .pyc files are not portable
> between versions, generally, excepting maintenance releases.
>
> -Peter[/color]

In fact this hidden recompilation, when it has to be applied to large
libraries, can impact performance considerably. I first came across this
when testing an application (which had its own, quite significant,
libraries) for compatibility between Cygwin and the standard Windows
interpreter, across different version numbers.

It was only when I started to look at file creation times I twigged that
running the program (for the first time only) under a different regime
was causing the libraries to be recompiled. Then the reason for the
inconsistency in run times was then obvious.

regards
Steve
--

http://www.holdenweb.com

http://pydish.holdenweb.com

Holden Web LLC +1 800 494 3119

[Steve Holden]

Re: installing 2.4

Peter Hansen wrote:
[color=blue]
> Matt Gerrans wrote:
>[color=green]
>> "Peter Hansen" <peter@engcorp. com> wrote:
>>[color=darkred]
>>> Only pure Python code can run without change on a newer interpreter.[/color]
>>
>>
>> Is the interpreter smart enough to rebuild a pyc (if the corresponding
>> py file is there of course) file that was built by a previous version?[/color]
>
>
> Yes. The .pyc files contain a magic cookie that is
> different in each major version, so 2.4 will recompile
> your 2.3 .pyc files. .pyc files are not portable
> between versions, generally, excepting maintenance releases.
>
> -Peter[/color]

In fact this hidden recompilation, when it has to be applied to large
libraries, can impact performance considerably. I first came across this
when testing an application (which had its own, quite significant,
libraries) for compatibility between Cygwin and the standard Windows
interpreter, across different version numbers.

It was only when I started to look at file creation times I twigged that
running the program (for the first time only) under a different regime
was causing the libraries to be recompiled. Then the reason for the
inconsistency in run times was then obvious.

regards
Steve
--

http://www.holdenweb.com

http://pydish.holdenweb.com

Holden Web LLC +1 800 494 3119