I propose that a 2.3.0 release is made forthwith (*) and that the floor version of Python is then raised to 2.6. With appropriate notification on the website front page.
We can then remove all the pre-2.6 hacks from the codebase and then look to ensuring the code runs on Python 3.2. Rationale for this has been rehearsed a number of times over the last few months: it is essential for SCons to have a Python 3 capability and that preserving Python 2.4 and 2.5 capability is an anchor prohibiting progress for no real benefit. With SCons 2.4.0 requiring Python 2.6 people using Pythons 2.4 or 2.5 will have SCons 2.3.0 or need to upgrade their Python. (*) Even without all the new D goodies :-) -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Scons-dev mailing list [email protected] http://two.pairlist.net/mailman/listinfo/scons-dev
