RELEASED Python 2.4.2 (final)

[Anthony Baxter]

On behalf of the Python development team and the Python community, I'm
happy to announce the release of Python 2.4.2 (final).

Python 2.4.2 is a bug-fix release. See the release notes at the
website (also available as Misc/NEWS in the source distribution) for
details of the more than 60 bugs squished in this release.

For more information on Python 2.4.2, including download links for
various platforms, release notes, and known issues, please see:

http://www.python.org/2.4.2

Highlights of this new release include:

- Bug fixes. According to the release notes, more than 60 have been
fixed, including bugs that prevented Python from working properly
on 64 bit HP/UX and AIX systems.

Highlights of the previous major Python release (2.4) are available
from the Python 2.4 page, at

http://www.python.org/2.4/highlights.html

Enjoy the new release,
Anthony

Anthony Baxter
anthony@python. org
Python Release Manager
(on behalf of the entire python-dev team)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDOpApDt3 F8mpFyBYRAgdxAK C85ssW10hOce4Jz BqEyGTqmBuQlwCb BfqX
iF7Qb1CSr6xO3FW wawPiPFM=
=aKTB
-----END PGP SIGNATURE-----

[Michael Ströder]

Fixes since 2.4.2c1? (was: RELEASED Python 2.4.2 (final))

Anthony Baxter wrote:[color=blue]
> On behalf of the Python development team and the Python community, I'm
> happy to announce the release of Python 2.4.2 (final).[/color]

Does that differ from 2.4.2c1? On Monday I noticed a crash in the test
suite on a box running Solaris 8. It seems I can build Python 2.4.1 and
run make test there without problems.

But being busy during the last days I did not have the time to track it
down and report a bug... :-/

Ciao, Michael.

[Terry Reedy]

Re: Fixes since 2.4.2c1? (was: RELEASED Python 2.4.2 (final))


"Michael Ströder" <michael@stroed er.com> wrote in message
news:5hkr03-jo6.ln1@nb2.str oeder.com...[color=blue]
> Does that differ from 2.4.2c1? On Monday I noticed a crash in the test
> suite on a box running Solaris 8. It seems I can build Python 2.4.1 and
> run make test there without problems.[/color]

There were are few additional fixes that Anthony thought were simple enough
to release after whatever 'in-house' testing but without a c2 release.
[color=blue]
> But being busy during the last days I did not have the time to track it
> down and report a bug... :-/[/color]

Apparently, no one else reported much of anythong either...
If necessary, 2.4.3 will come sooner than currently planned.

Terry J. Reedy

[Martin v. Löwis]

Re: Fixes since 2.4.2c1?

Michael Ströder wrote:[color=blue]
> Does that differ from 2.4.2c1? On Monday I noticed a crash in the test
> suite on a box running Solaris 8. It seems I can build Python 2.4.1 and
> run make test there without problems.[/color]

There is also a chance that you found a compiler bug. So reporting the
compiler you used would be essential.

Regards,
Martin

[Bugs]

Re: RELEASED Python 2.4.2 (final)

I downloaded the 2.4.2 Windows Binary Installer from python.org but when
I try to run python.exe I get the following in the console:
--------------------
ActivePython 2.4.1 Build 247 (ActiveState Corp.) based on
Python 2.4.1 (#65, Jun 20 2005, 17:01:55) [MSC v.1310 32 bit (Intel)] on
win32
Type "help", "copyright" , "credits" or "license" for more information.[color=blue][color=green][color=darkred]
>>>[/color][/color][/color]
--------------------
It says ActivePython 2.4.1 but I downloaded the 2.4.2 binary installer
from python.org and the python.exe executable I'm running is timestamped
9/28/2005 12:41PM... Any ideas what I'm doing wrong?

Thanks!

[Trent Mick]

Re: RELEASED Python 2.4.2 (final)

[Bugs wrote][color=blue]
> I downloaded the 2.4.2 Windows Binary Installer from python.org but when
> I try to run python.exe I get the following in the console:
> --------------------
> ActivePython 2.4.1 Build 247 (ActiveState Corp.) based on
> Python 2.4.1 (#65, Jun 20 2005, 17:01:55) [MSC v.1310 32 bit (Intel)] on
> win32
> Type "help", "copyright" , "credits" or "license" for more information.[color=green][color=darkred]
> >>>[/color][/color]
> --------------------
> It says ActivePython 2.4.1 but I downloaded the 2.4.2 binary installer
> from python.org and the python.exe executable I'm running is timestamped
> 9/28/2005 12:41PM... Any ideas what I'm doing wrong?[/color]

It is possible that the python.org installer didn't overwrite the
"python24.d ll" in the system directory (C:\WINDOWS\sys tem32). Try doing
this:

- manually delete C:\WINDOWS\syst em32\python24.d ll
- run the "repair" functionality of the python.org installer (you can
either do this from "Start | Settings | Control Panel | Add/Remove
Programs" or by just running the .msi file again

Then try running python again.

Trent


--
Trent Mick
TrentM@ActiveSt ate.com

[Bugs]

Re: RELEASED Python 2.4.2 (final)

Thanks Trent, you called it, it was an errant python24.dll left over
from an old ActiveState installation.

Trent Mick wrote:
[snip][color=blue]
>
> It is possible that the python.org installer didn't overwrite the
> "python24.d ll" in the system directory (C:\WINDOWS\sys tem32). Try doing
> this:
>[/color]
[snip]

[Martin v. Löwis]

Re: RELEASED Python 2.4.2 (final)

Trent Mick wrote:[color=blue]
> It is possible that the python.org installer didn't overwrite the
> "python24.d ll" in the system directory (C:\WINDOWS\sys tem32). Try doing
> this:[/color]

Even though this is apparently what happened, I'm puzzled as to why it
happened: shouldn't the version number of python24.dll in the pydotorg
installer be higher than the one in the ActivePython installer, and
shouldn't then Windows Installer overwrite the DLL?

The version in the pydotorg installer is 2.4.2150.1012.

Regards,
Martin

[Fuzzyman]

Re: RELEASED Python 2.4.2 (final)

On Thu, 29 Sep 2005 17:53:47 -0700, Bugs <dont@spam.me > wrote:
[color=blue]
>I downloaded the 2.4.2 Windows Binary Installer from python.org but when
>I try to run python.exe I get the following in the console:
>--------------------
>ActivePython 2.4.1 Build 247 (ActiveState Corp.) based on
>Python 2.4.1 (#65, Jun 20 2005, 17:01:55) [MSC v.1310 32 bit (Intel)] on
>win32
>Type "help", "copyright" , "credits" or "license" for more information.[color=green][color=darkred]
> >>>[/color][/color]
>--------------------
>It says ActivePython 2.4.1 but I downloaded the 2.4.2 binary installer
>from python.org and the python.exe executable I'm running is timestamped
>9/28/2005 12:41PM... Any ideas what I'm doing wrong?
>[/color]

I had problems updating from activestate 2.4 to activestate 2.4.1

I think it was caused by not uninstalling the original. This does mean
that even a *minor* version upgrade is a PITA. To do it cleanly all
extension modules have to be uninstalled and re-installed.

*sigh*

Fuzzyman
http://www.voidspace.org.uk/python
[color=blue]
>Thanks![/color]

[Michael Ströder]

Re: Fixes since 2.4.2c1?

Martin v. Löwis wrote:[color=blue]
> Michael Ströder wrote:
>[color=green]
>>Does that differ from 2.4.2c1? On Monday I noticed a crash in the test
>>suite on a box running Solaris 8. It seems I can build Python 2.4.1 and
>>run make test there without problems.[/color]
>
> There is also a chance that you found a compiler bug. So reporting the
> compiler you used would be essential.[/color]

It's gcc 3.0 installed by a Solaris 8 (probably outdated) package from

http://www.sunfreeware.com

I can dig further into on Tuesday. It's not my box.

Ciao, Michael.

[Steve Holden]

Re: RELEASED Python 2.4.2 (final)

Fuzzyman wrote:[color=blue]
> On Thu, 29 Sep 2005 17:53:47 -0700, Bugs <dont@spam.me > wrote:
>
>[color=green]
>>I downloaded the 2.4.2 Windows Binary Installer from python.org but when
>>I try to run python.exe I get the following in the console:
>>--------------------
>>ActivePytho n 2.4.1 Build 247 (ActiveState Corp.) based on
>>Python 2.4.1 (#65, Jun 20 2005, 17:01:55) [MSC v.1310 32 bit (Intel)] on
>>win32
>>Type "help", "copyright" , "credits" or "license" for more information.
>>
>>--------------------
>>It says ActivePython 2.4.1 but I downloaded the 2.4.2 binary installer[/color]
>[color=green]
>>from python.org and the python.exe executable I'm running is timestamped[/color]
>[color=green]
>>9/28/2005 12:41PM... Any ideas what I'm doing wrong?
>>[/color]
>
>
> I had problems updating from activestate 2.4 to activestate 2.4.1
>
> I think it was caused by not uninstalling the original. This does mean
> that even a *minor* version upgrade is a PITA. To do it cleanly all
> extension modules have to be uninstalled and re-installed.
>
> *sigh*
>[/color]
Not necessarily so. You should find the uninstall leaves all your local
additions in place in site-packages, immediately available when a new
minor version is installed.

Until 2.5, of course, *then* you'll need to reinstall.

regards
Steve
--
Steve Holden +44 150 684 7255 +1 800 494 3119
Holden Web LLC www.holdenweb.com
PyCon TX 2006 www.python.org/pycon/

[Peter Hansen]

Re: RELEASED Python 2.4.2 (final)

Martin v. Löwis wrote:[color=blue]
> Trent Mick wrote:
>[color=green]
>>It is possible that the python.org installer didn't overwrite the
>>"python24.dll " in the system directory (C:\WINDOWS\sys tem32). Try doing
>>this:[/color]
>
>
> Even though this is apparently what happened, I'm puzzled as to why it
> happened: shouldn't the version number of python24.dll in the pydotorg
> installer be higher than the one in the ActivePython installer, and
> shouldn't then Windows Installer overwrite the DLL?[/color]

Couldn't it also happen if the first time someone did an "admin" install
which (I believe) puts the DLLs in the system folder, and the next time
did just a non-admin install which doesn't do that? (Or am I
misunderstandin g the conditions under which c:\windows\syst em32 has
files written to it?)

-Peter

[Trent Mick]

Re: RELEASED Python 2.4.2 (final)

[Peter Hansen wrote][color=blue]
> Couldn't it also happen if the first time someone did an "admin" install
> which (I believe) puts the DLLs in the system folder, and the next time
> did just a non-admin install which doesn't do that? (Or am I
> misunderstandin g the conditions under which c:\windows\syst em32 has
> files written to it?)[/color]

I suppose that is possible. Martin, does python-2.4.2.msi install
python24.dll to the Python install dir for a "per-user" installation?

Note: I started this bug to track this and try to repro:

http://bugs.activestate.com/ActivePython/show_bug.cgi?id=41083

Trent

--
Trent Mick
TrentM@ActiveSt ate.com

[Trent Mick]

Re: RELEASED Python 2.4.2 (final)

[Fuzzyman wrote][color=blue]
> I had problems updating from activestate 2.4 to activestate 2.4.1
>
> I think it was caused by not uninstalling the original. This does mean
> that even a *minor* version upgrade is a PITA. To do it cleanly all
> extension modules have to be uninstalled and re-installed.
>
> *sigh*[/color]

As Steve said, uninstalling ActivePython 2.4 will leave your extensions
alone and then installing ActivePython 2.4.1 will install in the same
proper places so that all your extensions should just work.

Trent

--
Trent Mick
TrentM@ActiveSt ate.com

[Martin v. Löwis]

Re: RELEASED Python 2.4.2 (final)

Trent Mick wrote:[color=blue]
> I suppose that is possible. Martin, does python-2.4.2.msi install
> python24.dll to the Python install dir for a "per-user" installation?[/color]

Yes, that is supported. It would be good if Bugs could confirm that
he only deleted the wrong python24.dll, with the proper one being
installed in a different place already. His explanation
"you called it, it was an errant python24.dll left over from an old
ActiveState installation." is too imprecise to be able to tell
whether the two python DLLs where in the same location (requiring
a repair step) or in different locations (likely then resulting from
one being per-machine, and the other per-user).

Bugs?

Regards,
Martin