mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 15:05:49 +03:00
[GH-ISSUE #289] psycopg2-binary warnining #218
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#218
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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.txtneeds to be updated withpsycopg2==2.7.5 --no-binary psycopg2. Now my question: Should therequirements.txtbe updated?@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-essentialandlibpq-devon production machine(s) is not great, not terrible.