On 24 February 2012 00:21, Bináris <email@example.com> wrote:
Last time I proposed this there were voices saying some people are forced to use this historical version.
I think the main problem lies with RHEL and CentOS, both of which still ship Python 2.4. However, people running these OS'es are probably also smart enough to be able to do a manual python build.
As far as I am concerned, we should maybe even bump the minimum version to 2.6, which is the version the current debian stable uses. 2.5 was released in august 2006 (!), 2.6 in october 2008.
I also like the idea of using a wiki for getting responses - it allows people to stay anonymous if they want (by making a new account).
As for a date: I suggest something a few months in the future, say july or august. This gives people some time to update.
Last but not least: not supported does not necessarily mean we have to actively remove bits that work around quirks for a certain version; rather, it means we won't fix bugs due to an old python version.