By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,035 Members | 1,388 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,035 IT Pros & Developers. It's quick & easy.

RELEASED Python 2.4.1, release candidate 1

P: n/a
On behalf of the Python development team and the Python community, I'm
happy to announce the release of Python 2.4.1 (release candidate 1).

Python 2.4.1 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 bugs squished in this release.

Assuming no major problems crop up, a final release of Python 2.4.1 will
follow in about a week's time.

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

http://www.python.org/2.4.1/

Highlights of this new release include:

- Bug fixes. According to the release notes, several dozen bugs
have been fixed, including a fix for the SimpleXMLRPCServer
security issue (PSF-2005-001).

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
an*****@python.org
Python Release Manager
(on behalf of the entire python-dev team)

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

iD8DBQBCMFvKDt3F8mpFyBYRAv/4AJ9JxnsbICw7SY3iD0+ra4TS/HJ9YQCcDyXc
R87xUYy77e0bw5d0yZQH/Xg=
=sY2/
-----END PGP SIGNATURE-----

Jul 18 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Hi,

I have a problem with Python2.4 and win32com extensions, from Mark
Hammond's win32all package... I posted a few days back about a crash
when compiling files generated by win32com's 'makepy.py' utility.

Now these generated files, which are fine in Python 2.3.5, give a
syntax error on compile.

I posted a somewhat longer message on the python-dev mailing list but
since I'm not subscribe the message is awaiting moderator approval, and
I wanted to notify you of this problem ASAP.

The specific syntax errors are:

File
"D:\Python24\lib\site-packages\win32com\gen_py\00020813-0000-0000-C000-000000000046x0x1x3.py",
line 2591
return ret
^
SyntaxError: invalid syntax

File
"D:\Python24\lib\site-packages\win32com\gen_py\00020905-0000-0000-C000-000000000046x0x8x1.py",
line 3025
"StyleName": (3, 2, (8, 0), (), "StyleName", None),
"Value": (0, 2, (8, 0), (), "Value", None),
^
SyntaxError: invalid syntax
Eyeballing the files around these locations, I cannot detect any syntax
errors. And as I mentioned above, the exact same file compiles just
fine under Python2.3.5.
(And crashes the 2.4.0 interpreter)

regards,

--Tim

Jul 18 '05 #2

P: n/a
Does the workaround for the crash do anything for this problem ?

Mark has changed the makepy code to break up long lines, and
a new build of Pywin32 should be out before long.

Roger

"Tim N. van der Leeuw" <ti*************@nl.unisys.com> wrote in message
news:11*********************@f14g2000cwb.googlegro ups.com...
Hi,

I have a problem with Python2.4 and win32com extensions, from Mark
Hammond's win32all package... I posted a few days back about a crash
when compiling files generated by win32com's 'makepy.py' utility.

Now these generated files, which are fine in Python 2.3.5, give a
syntax error on compile.

I posted a somewhat longer message on the python-dev mailing list but
since I'm not subscribe the message is awaiting moderator approval, and
I wanted to notify you of this problem ASAP.

The specific syntax errors are:

File
"D:\Python24\lib\site-packages\win32com\gen_py\00020813-0000-0000-C000-000000000046x0x1x3.py",
line 2591
return ret
^
SyntaxError: invalid syntax

File
"D:\Python24\lib\site-packages\win32com\gen_py\00020905-0000-0000-C000-000000000046x0x8x1.py",
line 3025
"StyleName": (3, 2, (8, 0), (), "StyleName", None),
"Value": (0, 2, (8, 0), (), "Value", None),
^
SyntaxError: invalid syntax
Eyeballing the files around these locations, I cannot detect any syntax
errors. And as I mentioned above, the exact same file compiles just
fine under Python2.3.5.
(And crashes the 2.4.0 interpreter)

regards,

--Tim


----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----
Jul 18 '05 #3

P: n/a
Sorry, but I don't know what you mean with 'workaround for the
crash'...
The interpreter no longer crashes when trying to compile this file.
In Python2.4.0 I never saw any syntax error, there was just crash.
Now there is a syntax error, and I when I look at the code I don't spot
it.

regards,

--Tim

Jul 18 '05 #4

P: n/a
In the reply to your post about the crash, there
was a link to the bug report on Sourceforge that
includes a workaround. Specifically, remove the
mbcs encoding tag from the generated file. (or fromg
genpy.py itself so that it never gets put into a new
file) Does this do anything for the unwarranted
syntax errors ?

Roger

"Tim N. van der Leeuw" <ti*************@nl.unisys.com> wrote in message
news:11*********************@f14g2000cwb.googlegro ups.com...
Sorry, but I don't know what you mean with 'workaround for the
crash'...
The interpreter no longer crashes when trying to compile this file.
In Python2.4.0 I never saw any syntax error, there was just crash.
Now there is a syntax error, and I when I look at the code I don't spot
it.

regards,

--Tim



----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---
Jul 18 '05 #5

P: n/a
Hi Roger,

Thanks, I understand it now, I didn't yet receive in the mail any
replies to my post on py-dev when I read your post here! That's why it
didn't make any sense to me.

I didn't yet have a chance to try the workaround given in the
bug-report (remove MBCS encoding line). Hope to find time soon.

thanks,

--Tim

Jul 18 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.