Python 2.4 will be coming out "soon". I thought we might get a head-start so heres an ebuild and related files. I've only tested it on x86 and haven't enabled the arch specific patches that were in 2.3.4. I've been using 2.4 alpha3 since it came out and have only had problems with psyco and pyorbit, everything else I tried worked great. This is mainly for the Python herd and Python developers. Don't use this unless you know how to recover a dead python. Put the python.eclass in PORTDIR_OVERLAY/eclass for now. It takes care of the odd version number that Python betas have and I don't want to commit it to CVS just yet.
Created attachment 42531 [details] python-2.4_beta1.ebuild
Created attachment 42532 [details] files/depreorder.py
Created attachment 42533 [details] files/python-2.4-add_portage_search_path.patch
Created attachment 42534 [details] files/python-2.4-gentoo_py_dontcompile.patch
Created attachment 42535 [details] files/python-config-2.4
Created attachment 42536 [details] files/python-updater
Created attachment 42537 [details] PORTDIR_OVERLAY/eclass/python.eclass
Created attachment 42539 [details] PORTDIR_OVERLAY/eclass/python.eclass
Python 2.4 is final now. http://python.org Clock ticking to see which distro gets it in first. :->
Created attachment 45039 [details] python-2.4.ebuild Needs help with pkg_postinst(), see reference to python2.3 hard-coded in
Created attachment 45040 [details] python-updater Replaced hard-coded OLD_PY_VER=2.2 with smarter detection of old versions since now people could be upgrading from 2.2 or 2.3 to 2.4
Created attachment 45243 [details, diff] The ebuild without hard reference to python2.3 in pkg_postinst I've made a patch for ebuild, that solves the problem with hard-reference to python2.3 in pkg_postinst.
pyopengl-2.0.0.44 breaks, pyopengl-2.0.1.09 from pyopengl homepage works!
Closing - added to CVS, package.mask'd for testing. A couple of notes: Nick, thanks for patch# 45243. For now I'm leaving it out because I don't think it is necessary because the version of portage that used to keep portage.py etc. in site-packages is long-gone and shouldn't affect anyone upgrading to 2.4. Hanno, re: comment#13, please open a separate bug report for pyopengl and explain your problem; I emerged 2.0.0.44 using python2.4 without problems.
sorry for noise - now it compiled... :/
The /usr/portage/dev-lang/python/Manifest that I got from a Gentoo rsync mirror has some incorrect md5sums. The problem has persisted for a couple of days, through a couple of "emerge sync"s, so I think it's an outdated master Manifest, not just rsync mirror latency. (Unless someone *just* fixed it.) Once I did an "ebuild python-2.4.ebuild digest" to regenerate the Manifest, "emerge python" (with dev-lang/python in package.unmask to get 2.4) worked great.
The broken Manifest is already fixed as reported in bug 76892.
