Re: Python 2.3 support gone after 2.0.8 ?

Federico Di Gregorio <fog-NGVKUo/i/[email protected]>
Newsgroups gmane.comp.python.db.psycopg.devel
Organization initd.org
Message-ID <1242888082.4312.3.camel@erin>
Il giorno mer, 20/05/2009 alle 15.46 +0000, Simon Eisenmann ha scritto:
> Hi,
> 
> we are using psycopg a lot with python 2.3. Today i looked for updated
> versions and noticed that 2.0.9+ now requires python 2.4 or later.
> I am somewhat suprised to find such a massive compatibility change in a
> minor release and without any notice in the changelogs.
> As far as i can see this is only related to subprocess module usage in
> setup and to Py_VISIT, Py_CLEAR macro usage.
> 
> Is there any other reason why python 2.3 support was removed?

No real reason except wanting to support PY_VISIT (I guess, I didn't
make that changes). I agreed on them because usually the only reason to
work with such an old Python is embedding and Python 2.4 is much better
than 2.3 in my experience. So supporting 2.3 adds nothing.

I am sorry this change hurt you but 2.3 is so old that I didn't think
someone was still using it.

federico

-- 
Federico Di Gregorio                         http://people.initd.org/fog
Debian GNU/Linux Developer                                [email protected]
INIT.D Developer                                           fog-NGVKUo/i/[email protected]
 Lei: ma mi stai guardando l'ascella?
 Lui: no, ti stavo guardando una tetta.
                      -- Differenze fra il pensiero femminile e maschile

_______________________________________________
Psycopg mailing list
Psycopg-IAPFreCvJWPBWskQ1e/[email protected]
http://lists.initd.org/mailman/listinfo/psycopg
signature.asc (application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkoU940ACgkQvcCgrgZGjeuoFQCgoFpj6iSYMjiGGcVlkygWvN95
63sAn0csDbBrFrBNkoLjCfKGkK/uNdOS
=eq/M
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.