SQLAlchemy Migration Guides
Replace legacy declarative_base and declared_attr imports from sqlalchemy.ext.declarative.
Start here
Import declarative_base and declared_attr from sqlalchemy.orm instead of sqlalchemy.ext.declarative.
Stop before automation when: Mixed sqlalchemy.ext.declarative imports beyond the supported symbols. Indirect imports hidden behind helper modules.
from sqlalchemy.orm import declarative_base, declared_attr
Repo fit check
Run the matching scanner locally first. Read the free findings and manual alternatives; consider paid cleanup only if supported patterns repeat enough to justify the price.
Example scan summary
supported_findings: 38
manual_review_findings: 6
files_uploaded: 0
confidence: reviewableWhy this page exists
This is a clean import migration and a strong automation target.
Direct answer
Import declarative_base and declared_attr from sqlalchemy.orm instead of sqlalchemy.ext.declarative.
Example
from sqlalchemy.ext.declarative import declarative_base, declared_attr
from sqlalchemy.orm import declarative_base, declared_attr
Decision path
Start with the free scan, inspect the report, and only move to the cleanup pack if the repo has repeated supported patterns that are still expensive to fix by hand.
Before checkout
Price: $299.99 per team.
Use the exact-problem guides as a triage layer, then decide whether the repo is inside the supported subset.
FAQ
Import declarative_base and declared_attr from sqlalchemy.orm instead of sqlalchemy.ext.declarative.
Automate only the supported subset: Direct declarative_base import rewrites. Direct declared_attr import rewrites. Reporting when mixed legacy imports need closer review. Keep these cases in manual review: Mixed sqlalchemy.ext.declarative imports beyond the supported symbols. Indirect imports hidden behind helper modules. Files that already combine supported and blocked legacy patterns.
Use SQLAlchemy 1.4 to 2.0 Migration Cleanup Pack only when this pattern repeats across enough files that manual cleanup is still costly. Use the free report and upstream guide to evaluate fit. Buy only if repeated supported edits justify the price; no paid assessment is required.
Purchase fit
One matching page is not enough by itself. Run the local scan, then buy only when the same supported pattern appears often enough to matter.
Replace session.query(...).get(...), Session.query migration guide, Fix engine.execute(...) removal, Clean up joinedload_all(...), Fix select([..]) list syntax, Replace string join paths, Replace string loader options, Replace insert(..., values=...)
View all SQLAlchemy 1.4 to 2.0 Migration Cleanup Pack guides