pre-announce: Python 2.4a1 is about a month away
This is a pre-announcement that the first alpha of Python 2.4 is about a month away. The purpose of this notice is to give people a heads up - if you have a bug that you want to see fixed for 2.4, start looking at it now.
Fixes are welcome through the release cycle, although after the first beta fixes that result in a change to behaviour will be much less likely to be accepted.
So, if you have a bug you want to see fixed, what should you do?
- If it's not logged on SF, log it. - If it's logged, consider adding a patch that fixes the problem, or at least a simple test case that demonstrates the bug. - If someone else has supplied a fix, see if this fix works for you, and post your results to the bug. - If there's a working fix, feel free to add a note asking for the fix to go into CVS. The SF bug tracker for Python has a _lot_ of bugs in it, and it's easy for bugs to be overlooked.
If you're just interested in what's coming up in 2.4, see the current development version of the "What's New in 2.4" document at http://www.python.org/dev/doc/devel/whatsnew/whatsnew24.html
On behalf of the python-dev team, thanks! Anthony
[This form of pre-announcement will hopefully become a part of the release process for all future releases of Python, both major and bugfix releases, to give people a chance to get their bugfix-of-choice submitted in time. Any feedback on this process, please feel free to email me]
On Mon, 2004-05-31 at 11:39, Anthony Baxter wrote:
This is a pre-announcement that the first alpha of Python 2.4 is about a month away. The purpose of this notice is to give people a heads up - if you have a bug that you want to see fixed for 2.4, start looking at it now.
I just wanted to note for the record that the ast-branch did not get merged by the beginning of May and won't be included in Python 2.4. (At PyCon, we agreed to finish it by then or hold off.)
The ast-branch is actually in quite good shape, but I didn't have time to finish it before starting my new job. It handles every major source construct correctly; there are a few corner cases (in exec for example) that are off and there are a number of error handling / memory management issues to sort out.
It's far enough along that development is fairly comfortable on the branch. setup.py compiles and executes correctly as do almost all of the regression tests.
I think the most likely next step is to merge the head to the branch so that it keeps up with the evolution of the language. Merging changes from the head will identify changes that the compiler is expected to handle. I don't know when that will happen -- perhaps early fall if it's left to me.
Jeremy
participants (2)
-
Anthony Baxter -
Jeremy Hylton