Am 24.03.2020 um 05:46 schrieb Justin Pryzby:
This patch got stuck due to our limited understand of python's
dynamic loading of shared libraries. I picked it up again ince I
have some downtime..
Thanks for working on this problem. Would be great if we could resolve
it. Otherwise it always hinders us supporting the latest features.
> Since it's BIND_NOW, it means that any python program linked to
> pygres willsimply fail at startup in the unlikely even that it was
> compiled against libpq for PG12 but runs against an lib older
It's unlikely when you compile yourself, but Windows users normally
don't do that since they have no compiler. So if we ship a version that
was compiler against Pg12, it will not run for users with Pg11 installed
on their machine. On the other hand, Windows DLL work a little bit
differently anyway, maybe we can find a different solution there.
Maybe where we release binaries (currently only for Windows) we could
ship them with a matching libql dll that will be installed with Pip
alongside the PyGres dll? Or maybe link the pqlib statically into the
PyGres dll in that case? This would make it even more convenient for
Windows users since they don't need to install Postgres.
-- Christoph
_______________________________________________
PyGreSQL mailing list
PyGreSQL@Vex.Net
https://mail.vex.net/mailman/listinfo/pygresql
