RELEASED Python 2.3.3 (release candidate 1)
On behalf of the Python development team and the Python community, I'm happy to announce the release of Python 2.3.3 (release candidate 1).
Python 2.3.3 is a bug-fix release of Python 2.3. A couple of serious bugs related to weakrefs and the cyclic garbage collector have been fixed, along with a number of bugs in the standard library. See the release notes on the web page for more details.
For more information on Python 2.3.3c1, including download links for various platforms, release notes, and known issues, please see
Highlights of this new release include:
- A couple of serious bugs in the interactions of weakrefs and cyclic GC have been squashed. - At shutdown, the second call to the cyclic garbage collector has been removed. This caused more problems than it solved. - The xml.parsers.expat module now provides Expat 1.95.7. - urllib2's HTTP Digest Auth support works again. - See http://www.python.org/2.3.3/NEWS.html for other bugfixes.
Highlights of the previous major Python release (2.3) are available from the Python 2.3 page, at
http://www.python.org/2.3/highlights.html
A final version of Python 2.3.3 should follow in a couple of weeks, just in time for your Christmas stockings.
Enjoy the new release, Anthony
Anthony Baxter anthony@python.org Python 2.3.x Release Manager (on behalf of the entire python-dev team)
While building and trying out the windows installer yesterday, I had some crashes in pydocgui.pyw (the module documentation server), both on win98SE and on XP Pro. The crash ocurred when it was closed, and it seems only when the test suite was also installed (usually it also finds something in the test suite). Win98 was unhelpful as usual in only showing the top of the machine stack, winXP displayed a message box showing an access violation in TclNotifier.
I were not able to debug this, because I couldn't get Tkinter to work in the version running from the build dir, and I had no more time - I assume there are some env vars to be set so that it finds the tcl and tk dlls.
I could not reproduce the problem with the final built which is no out in the cold, so I assume it was a temporary problem. But it would be nice if other people could try this out as well before this comes back later on me.
Thanks,
Thomas
[Thomas Heller, on 5 Dec]
While building and trying out the windows installer yesterday, I had some crashes in pydocgui.pyw (the module documentation server), both on win98SE and on XP Pro. The crash ocurred when it was closed, and it seems only when the test suite was also installed (usually it also finds something in the test suite).
...
I could not reproduce the problem with the final built which is no out in the cold, so I assume it was a temporary problem.
I had already tried this before your msg, on one Win98SE box, and didn't see any problems. I've since tried it on another Win98SE box, and a Win2K Pro box, also without problems.
I can't get my Python 2.3.3c1 program to work. It keeps core dumping (leaving python.core). I'm not doing anything strange, just documented stuff from the manuals. I tried 'gdb -c python.core' and then using 'back', but there are no labels compiled in (I hate that...); how can I get the labels to be included? "./configure --debug" doesn't work. I assume without the labels the numbers are meaningless. Running this under OpenBSD 3.2. Then, where should I submit my core dump (if anywhere?)?
I used to have the URL bookmarked, but just upgraded and lost most of my old bookmarks....
John
John> Then, where should I submit my core dump (if anywhere?)?
Submit bug reports here:
http://sourceforge.net/tracker/?group_id=5470&atid=105470
but please don't attach core files (they are too big and nobody will be able to make use of them). Instead, attach a small Python script which demonstrates how to generate a core dump.
Skip
On Dec 15, 2003, at 6:55 AM, Skip Montanaro wrote:
John> Then, where should I submit my core dump (if anywhere?)?Submit bug reports here:
http://sourceforge.net/tracker/?group_id=5470&atid=105470
Thanx, OK, I logged in, and got the main page which confirmed my login was good. But I cannot find any links that allow me to submit bug reports. Where is the link? I cannot find it.
On the left part of the screen, I get this? Does one of these links go to the bug reporting page?
SF.net Resources
· Site Docs · Site Status · Site Map · SF.net Supporters · Compile Farm · Foundries · Project Help Wanted · New Releases · Get Support
There are two columns in the main page.... One titled...
My Assigned Tracker Items and another titled My Tasks
I see no place on this site where there is a link I can use to report any bugs... If it don't say "Bug reporting" or anything similar, then I need to know the name of the link, because it clearly isn't very obvious.
Another thing also.... if I click on Python Bugs link in the left column, it goes into a "Browse Bugs" section, but then there is yet another "Please log in" in red. OK, so I log in again..... but when I do, I don't see the "Submit New" button, but I do see a "Submit New" link above the buttons. I DO have Cookies enabled of course, but I'm using Safari browser. By the way, I DO click on SSL. I just tried it with IE and get the same results....
I think I finally submitted it.... but can I go back and add some additional info? If so, how?
Further details on the Python core dump:
It core dumps (segmentation fault) when I check the database for a certain key. The offending statement is: x=database.has_key(keystring). database is open and otherwise normal. The database is "gdbm-1.8.3". The offending key is "3012a3ec5c796329fee7c242d4df00d6".
John
>> Submit bug reports here: >> >> http://sourceforge.net/tracker/?group_id=5470&atid=105470
JD> Thanx, OK, I logged in, and got the main page which confirmed my JD> login was good. But I cannot find any links that allow me to submit JD> bug reports. Where is the link? I cannot find it.
Pop up that page (while logged in) and search for "Submit New".
JD> There are two columns in the main page.... One titled...
JD> My Assigned Tracker Items and another titled My Tasks
Wrong page. Once you log in, SF takes you to your "my sf.net" page. After logging in, pop back to
http://sourceforge.net/projects/python
then poke the "Bugs" link, which will take you to the bug tracker (the first URL above).
JD> Another thing also.... if I click on Python Bugs link in the left JD> column, it goes into a "Browse Bugs" section, but then there is yet JD> another "Please log in" in red.
Sounds like you have cookies disabled. To use SourceForge you need to run with cookie support turned on.
Skip
On Mon, Dec 15, 2003, Skip Montanaro wrote:
Sounds like you have cookies disabled. To use SourceForge you need to run with cookie support turned on.
...and you can't use Lynx, either. :-(
Aahz aahz@pythoncraft.com writes:
On Mon, Dec 15, 2003, Skip Montanaro wrote:
Sounds like you have cookies disabled. To use SourceForge you need to run with cookie support turned on.
...and you can't use Lynx, either. :-(
It seems that you can, so long as you "attach" /dev/null to the bug report each time you do anything...
Cheers, mwh
On Tue, Dec 16, 2003, Michael Hudson wrote:
Aahz aahz@pythoncraft.com writes:
On Mon, Dec 15, 2003, Skip Montanaro wrote:
Sounds like you have cookies disabled. To use SourceForge you need to run with cookie support turned on.
...and you can't use Lynx, either. :-(
It seems that you can, so long as you "attach" /dev/null to the bug report each time you do anything...
Looks like SF has finally fixed things to work with Lynx.
JD lists@webcrunchers.com writes:
Running this under OpenBSD 3.2. Then, where should I submit my core dump (if anywhere?)?
You should submit bug reports to sf.net/projects/python, and provide a link to the core dump on a server of your control (as SF has a limit on file upload size).
Please understand that several months, or even years, may pass until such a bug report is looked at, so if you actually need this to work, you will have to investigate it in more detail.
On Unix, Python is, by default, compiled with symbols if the compiler is gcc. To find out why gdb does not see symbols, you should post a few lines of make output, showing typical compiler and linker invocations.
Regards, Martin
participants (8)
-
Aahz -
Anthony Baxter -
JD -
martin＠v.loewis.de -
Michael Hudson -
Skip Montanaro -
Thomas Heller -
Tim Peters