Handling psycopg2-binary dependency #143
Comments
misuzu
changed the title
13 tasks
|
This is nixpkgs python-check-deps hook failing to find psycopg2-binary. The hook is using Python packaging metadata to ensure the environment that is present in the build outputs. Normally I'd tell you that you need to package a wheel in your Python overlay, but in this instance I think we should fix it in nixpkgs by adding a fake See NixOS/nixpkgs#337621. |
|
Not an issue in |
adisbladis
added a commit
to adisbladis/nixpkgs
that referenced
this issue
Aug 29, 2024
Pscycopg2-binary is normally used in Python development to avoid having to build psycopg2 from source. In nixpkgs we always want ot build from source whenever possible, but it can still be useful to provide a psycopg2-binary package. This "fake" package exists to satisfy a dependency on psycopg2-binary, but still use the build from psycopg2. cc @misuzu nix-community/pyproject.nix#143
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Suppose I have the psycopg2-binary package in a pyproject.toml, the nixpkgs doesn't have this package so this won't evaluate.
But nixpkgs has the equivalent psycopg2 package.
How do I tell pyproject.nix to use psycopg2 instead of psycopg2-binary without editing the pyproject.toml?
I've tried just making an alias (
psycopg2-binary = psycopg2;), but it fails to build (psycopg2-binary not installed).The text was updated successfully, but these errors were encountered: