[GH-ISSUE #289] psycopg2-binary warnining #218

Closed
opened 2026-02-25 23:41:39 +03:00 by kerem · 1 comment
Owner

Originally created by @SuperSandro2000 on GitHub (Sep 29, 2019).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/289

When I run the project I get the following warning from psycopg2

/usr/local/lib/python3.7/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>.

The underlying issue and cause if this warning is discussed here https://github.com/psycopg/psycopg2/issues/674
and a fix is mentioned here https://github.com/psycopg/psycopg2/issues/674#issuecomment-401840661.

After reading it I am still not quite sure why but I think the requirements.txt needs to be updated with psycopg2==2.7.5 --no-binary psycopg2. Now my question: Should the requirements.txt be updated?

Originally created by @SuperSandro2000 on GitHub (Sep 29, 2019). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/289 When I run the project I get the following warning from psycopg2 ```` /usr/local/lib/python3.7/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>. ```` The underlying issue and cause if this warning is discussed here https://github.com/psycopg/psycopg2/issues/674 and a fix is mentioned here https://github.com/psycopg/psycopg2/issues/674#issuecomment-401840661. After reading it I am still not quite sure why but I think the ``requirements.txt`` needs to be updated with `` psycopg2==2.7.5 --no-binary psycopg2``. Now my question: Should the ``requirements.txt`` be updated?
kerem closed this issue 2026-02-25 23:41:39 +03:00
Author
Owner

@cuu508 commented on GitHub (Sep 30, 2019):

We will want to move to psycopg 2.8 series sooner or later.
At that point we will have to choose between having psycopg2 or psycopg2-binary in requirements.txt.

The documentation at http://initd.org/psycopg/docs/install.html#binary-install-from-pypi recommends to use the source version (more details in that link) . I'm leaning in that direction too. Needing build-essential and libpq-dev on production machine(s) is not great, not terrible.

<!-- gh-comment-id:536473444 --> @cuu508 commented on GitHub (Sep 30, 2019): We will want to move to psycopg 2.8 series sooner or later. At that point we will have to choose between having psycopg2 or psycopg2-binary in `requirements.txt`. The documentation at http://initd.org/psycopg/docs/install.html#binary-install-from-pypi recommends to use the source version (more details in that link) . I'm leaning in that direction too. Needing `build-essential` and `libpq-dev` on production machine(s) is not great, not terrible.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/healthchecks#218
No description provided.