Summary
The published aws-advanced-python-wrapper==3.0.0 package registers the PostgreSQL SQLAlchemy dialect postgresql+aws_wrapper_psycopg, but the module referenced by that entry point is not present in the installed wheel.
This prevents use of the documented SQLAlchemy integration for PostgreSQL.
Expected behavior
The documented engine should construct successfully:
from sqlalchemy import create_engine
engine = create_engine("postgresql+aws_wrapper_psycopg://")
Actual behavior
It fails before making any database connection:
ModuleNotFoundError: No module named 'aws_advanced_python_wrapper.sqlalchemy.pg_orm_dialect'
Reproduction
from importlib.metadata import distribution
from sqlalchemy import create_engine
package = distribution("aws-advanced-python-wrapper")
print(package.version)
print([
str(path)
for path in package.files
if "sqlalchemy" in str(path) or "psycopg" in str(path)
])
create_engine("postgresql+aws_wrapper_psycopg://")
Observed with:
aws-advanced-python-wrapper==3.0.0
- Python 3.14
- SQLAlchemy 2.x
The package metadata includes this SQLAlchemy entry point:
postgresql.aws_wrapper_psycopg =
aws_advanced_python_wrapper.sqlalchemy.pg_orm_dialect:SqlAlchemyOrmPgDialect
However, the installed package contains the MySQL ORM dialect but not pg_orm_dialect.py.
Why this matters
The current documentation says PostgreSQL must use the wrapper-specific SQLAlchemy dialect because the stock postgresql+psycopg dialect rejects the wrapper connection during initialization. Without the PostgreSQL dialect module, the documented failover-aware SQLAlchemy integration cannot be used from the published package.
Could you confirm whether this is a packaging omission in 3.0.0, and publish a corrected release?
Summary
The published
aws-advanced-python-wrapper==3.0.0package registers the PostgreSQL SQLAlchemy dialectpostgresql+aws_wrapper_psycopg, but the module referenced by that entry point is not present in the installed wheel.This prevents use of the documented SQLAlchemy integration for PostgreSQL.
Expected behavior
The documented engine should construct successfully:
Actual behavior
It fails before making any database connection:
Reproduction
Observed with:
aws-advanced-python-wrapper==3.0.0The package metadata includes this SQLAlchemy entry point:
However, the installed package contains the MySQL ORM dialect but not
pg_orm_dialect.py.Why this matters
The current documentation says PostgreSQL must use the wrapper-specific SQLAlchemy dialect because the stock
postgresql+psycopgdialect rejects the wrapper connection during initialization. Without the PostgreSQL dialect module, the documented failover-aware SQLAlchemy integration cannot be used from the published package.Could you confirm whether this is a packaging omission in 3.0.0, and publish a corrected release?