Skip to content

test(postgres): skip the bind-site tests when the postgres extra is absent — main is red #464

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jphein merged 1 commit into from
Sep 11, 2026
Merged

test(postgres): skip the bind-site tests when the postgres extra is absent — main is red #464

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions tests/test_postgres_unstorable_bytes.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,9 +199,15 @@ def connect(self, dsn, **kwargs):


def _real_sql():
from psycopg import sql
"""Real psycopg SQL composition — these tests assert on bound parameters.

return sql
The ``test-linux`` CI job installs mempalace without the ``postgres``
extra, so psycopg is absent there and importing it at module scope would
fail collection. Skip only the four bind-site tests that genuinely need
SQL composition; the pure-logic scrub tests above run everywhere, which is
where the behaviour under test actually lives.
"""
return pytest.importorskip("psycopg.sql", reason="requires the postgres extra")


@pytest.fixture()
Expand Down
Loading