--=-Xm9AE9U4169Yce8G4HHa
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi *,

I don't know if this is really a bug but surely is something that is
giving a lot of problems to psycopg (pyhton/postgresql adapter). psycopg
1.1.11+ checks for libpq version at runtime and, if available uses the
new protocol api (mainly to extract non-localized error codes after
errors). now, the problem is that a *lot* of users have two different
libpq versions of their systems and usually psycopg gets compiled
against 7.4 and runtime-linked against 7.3, resulting in an error
(symbols not found).

the question is: there is any special reason to change the api of a
library and *not* change the soname? having changed the soname of the
library would have avoided this kind of problems.

thank you in advance for your time,
federico

--=20
Federico Di Gregorio http://people.initd.org/fog
Debian GNU/Linux Developer fog (AT) debian (DOT) org
INIT.D Developer fog (AT) initd (DOT) org
We are all dust, Saqi, so play the lute
We are all wind, Saqi, so bring wine. -- Omar Khayam

--=-Xm9AE9U4169Yce8G4HHa
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBAqcokvcCgrgZGjesRAmKnAKDC0UhAmq2RfVAa/qAbuLkcH1ZJqACdECa8
phQjYDCV+AJt1ttpelEngeA=
=MvEL
-----END PGP SIGNATURE-----

--=-Xm9AE9U4169Yce8G4HHa--