I would like to add two figures to the discussion :
 * security-fix support for Python 2.5 ended on May 2011 with 2.5.6
 * security-fix support for Python 2.6 ended on October 2013 with 2.6.9

It will be difficult to avoid breaking compatibility with obsolete Python, 
because not all developers have all versions of Python available in their 
working environment.
To make it easier for everyone, we have setup a Travis-CI to run the tests 
on every commit and pull request.
It helps to be more robust and mitigate the risk of regression. However 
Travis-CI does not support Python older that 2.6.

Another argument to drop support for older Python is to prepare the future, 
because it is a lot more difficult to adapt the code for Python 3 when we 
try to preserve compatibility with archaic Python versions at the same time.
With Python 2.6 as a minimal requirement, we can use some modern constructs 
which help if we want to work towards single-source compatibility with 
Python 3 some day.

Because of the above considerations, I vote for 2.6 only for the 8.7 (or 9) 
release.
The version 8.6.9 would be recommended for people which are stuck with 
Python 2.5 or 2.4.


-- 
Florent Xicluna

Le jeudi 29 mai 2014 11:31:42 UTC+2, Lex Trotman a écrit :
>
> Currently Asciidoc supports Python back to 2.4. 
>
> There are some library elements from that era which are now 
> deprecated.  The replacement libraries are only available on 2.5. 
> Whilst the warnings have so far simply been silenced, that is not a 
> real fix. 
>
> Therefore it is proposed that the oldest supported version be advanced 
> to Python 2.5. 
>
> If anybody knows of any reason why this should not be done speak up now. 
>
> Cheers 
> Lex
>

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.

Reply via email to