increasing the python requirement

[jbowtie at amathaine.com]

On Fri, Jan 7, 2011 at 12:12 PM, John Arbash Meinel
<john at arbash-meinel.com> wrote:
> Which means a lot of invasive code changes to be able to support 2.4 +
> 3.0 via 2to3.

>
> You can always not use features that aren't available in py2.
>

If we ever get to the point where we're coding in 3.x, I think I'd
expect 2.7 to be the minimum supported version which has backported
enough 3.x features to make 3to2 viable.

However, I would expect our minimum version to go from 2.4 -> 2.6 ->
2.7 -> 3.x, unless 3.x unexpectedly gains critical mass for some
reason. Meaning that by the time we switch to writing 3.x code we
won't be supporting 2.x anymore (though I'm sure someone will maintain
a branch off the last official 2.x release for some years).