Re: Noisy dependency on psycopg2 versus psycopg2-binary

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: Noisy dependency on psycopg2 versus psycopg2-binary
Дата
Msg-id CA+OCxoxEB4GJCYBja-5f70v2o-Fe+SyS_2NFazYGPc9fwiX+Ug@mail.gmail.com
обсуждение исходный текст
Ответ на Noisy dependency on psycopg2 versus psycopg2-binary  (Shaheed Haque <srhaque@theiet.org>)
Ответы Re: Noisy dependency on psycopg2 versus psycopg2-binary  (Shaheed Haque <srhaque@theiet.org>)
Список pgadmin-support
Hi

On Tue, Mar 19, 2019 at 10:19 AM Shaheed Haque <srhaque@theiet.org> wrote:
Hi,

I'm still on 4.2, but checking the release notes for 4.3 suggests it too has the problem of being dependent on psycopg2 versus psycopg2-binary. This results in the annoying message:

/usr/local/lib/python3.6/dist-packages/psycopg2/__init__.py:144: UserWarning: The psycopg2 wheel package will be renamed from release 2.8; in order to keep installing from binary please use "pip install psycopg2-binary" instead. For details see: <http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.

My package also had this problem, and the fix was to replace the reference to psycopg2 with  psycopg2-binary in setup.py. I hope that helps,

This is not a problem for us - it's completely intentional. We need full control over the build of psycopg2, so we can ensure that it, and the libpq, OpenSSL, Gettext and other dependent libraries as well as our runtime and Python build are all using the same compiler and compiler flags etc. 

If there's a way that we could conditionally use psycopg2-binary *just* for the wheel, I'd be open to that, but I'm not sure how we could do it.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

В списке pgadmin-support по дате отправления:

Предыдущее
От: Polgár Benedek
Дата:
Сообщение: pgadmin 4 missing features
Следующее
От: Dave Page
Дата:
Сообщение: Re: pgadmin 4 missing features