A while ago, I asked which version of python we were assuming.

The answer came back that we really weren't; on Mac and Linux,
we were using the system's python.

So I'll ask again:  how much support is required for which python?

Is it OK if certain features require at least Python x.x?

Is it OK if certain features work better with at least Python x.x?

When newer python offers a much cleaner way to do something, is it
OK to write it that way and require that people running older pythons
do a transformation on the code as part of setup, so long as the
transformation can be automated and is included?

Is it OK to use modules that are in the standard library of newer
pythons, but not older pythons, so long as there is a workaround?
Can this workaround be "download the library from xxx, it does
work for you."?  Should we include the library in our distribution?
How about a litelib version that does a minimal job (so they don't
*have* to download anything) and suggests that they upgrade to the
real library or a newer python?

FWIW, I would like to use several features that don't appear in 
Python 1.5, a few that don't appear until 2.3, and even a few 
that won't become standard until 2.4.  (I know I would have to 
distribute versions for those.)

-jJ
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev

Reply via email to