On Mon, Aug 21, 2017 at 5:48 PM, Damjan Georgievski via arch-general <
arch-general@archlinux.org> wrote:
> > I use psycopg2 for postgres access in my pyramid web-app, and like most
> > (all?) python developers all the dependencies are in a virtualenv,
> > including psycopg2 itself.
> >
> > This m
So reinstalling psycopg2 with `pip install --no-binary :all: psycopg2`
works. Still wondering whether this is an issue to raise upstream.
On Mon, Aug 21, 2017 at 5:41 PM, Oon-Ee Ng wrote:
> I use psycopg2 for postgres access in my pyramid web-app, and like most
> (all?) python developers all the
> I use psycopg2 for postgres access in my pyramid web-app, and like most
> (all?) python developers all the dependencies are in a virtualenv,
> including psycopg2 itself.
>
> This means, of course, that the psycopg2 wheel is precompiled.
>
> With the recent glibc-2.26 update, I can no longer impor
I use psycopg2 for postgres access in my pyramid web-app, and like most
(all?) python developers all the dependencies are in a virtualenv,
including psycopg2 itself.
This means, of course, that the psycopg2 wheel is precompiled.
With the recent glibc-2.26 update, I can no longer import psycopg2.
4 matches
Mail list logo
