Re: Supported versions of Python

[Edward B. <ed...@ba...>]

Hi there,

Tony Meyer wrote:

>  * Continue with the 2.x line (the last time I checked, there is at
> least 2.7 scheduled, and there could be a 2.8 or even 2.9), including
> support for older versions of 2.x.

Python 2.x is still the latest version of Python on 99% of machines 
running Python.  Until distros catch up, I think it makes sense to view 
Python 3.x as the future, e.g. not the present.  There's little risk in 
continuing with Python 2.x as development platform for the next 3 years 
(probably longer).  Since Python 3.x is intentionally not backwards 
compatible, adoption will be slow.

>  * Create a 3.x branch, and have separate releases for 2.x and 3.x
> (note that this is obviously the most work, since there are two
> diverging sets of code to maintain and develop, so there would have to
> be a real need for this).

Ideally, one set of code supports BOTH 2.x and 3.x.  You could add a 
configuration variable that asks for Python version and where there are 
code differences between the two, run different code blocks.  I admit it 
could get very messy doing this but users would be happy.  When 2.x 
becomes legacy, you can just remove these conditional blocks.

>  * Start discontinuing support for old versions of Python after the
> next Pyzor release (coming very soon).  I suspect that 2.5 could be
> maintained while supporting a 3.x version (using the 2to3 tool),
> although it's possible that 2.6 would have to be the minimum required.
>  This wouldn't be a "rewrite", just tidying up older code (e.g. the
> style of raising exceptions).
> 
> Obviously, old versions of Pyzor continue to work with old versions of
> Python, no matter what.  The upcoming Pyzor release should work with
> any 2.x version of Python.

Eventually, Python 3.x support will be great and much desired.  But I 
don't think the demand is there yet.  Users just want a working Pyzor 
that does what Pyzor claims to do.  If Python 3.x development today 
comes at the expense of a stable 2.x version, then I say bad idea.  But 
if both 2.x and 3.x can be supported equally well, then go for it.

Ed

> 
> Thanks,
> Tony