Re: [Pypgsql-users] How important is Python 2.1 compatibility?

[Adam B. <ad...@po...>]

Hallo Billy,

I apologize that I haven't written before, but I had to finish some
urgent projects and I haven't much time for anything else. :(  Of
course I downloaded pyPgSQL 2.1 as soon as it was announced here.  It
works very good, especially this new transaction isolation level
setting, which I asked for some time ago :))  I improved most of my
applications to use this feature and I am glad to see that everything
is OK, and even works better than before.  I wonder why people still
use other Python libraries for PostgreSQL, this one is the best! :^))

> 1.  Should pyPgSQL drop compatibility with versions of Python previous to 
> version 2.2?

It really doesn't matter for me.  My applications work with both
Python 2.1 and 2.2 (I don't use many features of Python 2.2 yet).
However, I think that it is not good for any project to keep backward
compatibility -- it always equals to more complicated code.
Even PostgreSQL evolves and some SQL commands and syntax become
obsolete, so many programmers will have to improve their programs.

The only problem arises when someone uses libraries which don't work
with newer Python releases.  For example something is wrong with
stable branch of wxPython/wxGTK library and I still haven't figured
what it could be.  The application crashes (core dumped etc.) and I
still have to use Pyhton 2.0 (!) to run it.  Hopefully I am now
switching to PyGTK and this problem will soon disappear, even if not
removed by a next wxPython version.

Generally, I vote for option 1! :)

Regards,

-- 
Adam Buraczewski <ad...@po...> * Linux registered user #165585
GCS/TW d- s-:+>+:- a- C+++(++++) UL++++$ P++ L++++ E++ W+ N++ o? K? w--
O M- V- PS+ !PE Y PGP+ t+ 5 X+ R tv- b+ DI? D G++ e+++>++++ h r+>++ y?