sqlalchemy / sqlalchemy/alembic
pluggable impls
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 375
- PR merge metrics
- No merged PRs in 30d
Description
Migrated issue, originally created by Michael Bayer (@zzzeek)
to support any number of dialects, the system by which we load "impls" should use the PluginLoader system from SQLAlchemy, and support entrypoints as well as local registration. Similarly, there should be a test suite just like that of SQLAlchemy which runs a standard suite of "operation directive" tests on any arbitrary impl. This implies the task of upgrading alembic's testing platform to use the SQLAlchemy library that now supports py.test.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Alembic's current impl-loading and testing-platform entry points, then compare them with SQLAlchemy's PluginLoader and py.test-supported test suite. Done means dialect implementations can register locally or through entrypoints, and arbitrary impls run the standard operation-directive tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlalchemy
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100