Hi,
- For 1.9, it's a little late to make any changes, but I would consider
dropping py2.5 support (and converting to the 'except' 'as' syntax),
since for 1.9 py3 support is more important than py2.5 support.
Thoughts?
I'd rather not mess with the 1.9 branch at this point ... we're so close
to the release (I hope).
-- Brane
as a thought for the 1.9 case:
In case you do not want to drop py2.5 support for 1.9 because it's
released stating that minimum support already, would it be an option to
still support py3 in a following patch (1.9.1)? For instance by
providing py-script versions for older as well as later versions?
Reasoning would be that given that SVN-versions have a lifetime of
roughly 2 years before the successive version is released it'd be quite
a limitation if that'd only work with a very old python version...
As an alternative approach: You'd also consider mentioning a minimum
requirement of python 2.6 just in the docs (no code changes yet) and
then release 1.9.1 with the actual "fixes". So technically then even
post release you would not change the minimal system requirements.
(just some thoughts from a user's point of view, if that input would be
of any benefit)
Regards,
Stefan
