SQLAlchemy Migration Guides
Drop the legacy select([..]) wrapper and move to direct select(...) calls.
Start here
Drop the wrapper list and pass the columns or table directly into select(...).
Stop before automation when: Calls already mixed with broader query redesign. Generated code that obscures the argument list.
stmt = select(user_table)
stmt = select(User.name, User.email)
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 exactly the kind of syntax change that good codemods should automate first.
Direct answer
Drop the wrapper list and pass the columns or table directly into select(...).
Example
stmt = select([user_table])
stmt = select([User.name, User.email])
stmt = select(user_table)
stmt = select(User.name, User.email)
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
Drop the wrapper list and pass the columns or table directly into select(...).
Automate only the supported subset: Deterministic select([..]) to select(..) rewrites. Repo reporting for the syntax bucket. Links to the broader SQLAlchemy guide set. Keep these cases in manual review: Calls already mixed with broader query redesign. Generated code that obscures the argument list. Files that also contain unsupported execution-path changes.
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(...), Replace string join paths, Replace string loader options, Move sqlalchemy.ext.declarative imports to sqlalchemy.orm, Replace insert(..., values=...)
View all SQLAlchemy 1.4 to 2.0 Migration Cleanup Pack guides