sqlalchemy / sqlalchemy/alembic
Allow overriding of script.py.mako path in generate_revision
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 375
- PR merge metrics
- No merged PRs in 30d
Description
We have a use case where our script.py.mako is stored in a central location to be shared by multiple sets of alembic revisions. We currently just copy it into each project's scripts directory but that's not ideal.
It looks like this could be allowed by adding an optional kw arg to generate_revision which is then passed into _generate_template, using the existing value as a default.
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 in alembic/script/base.py at generate_revision and follow its call to _generate_template. Add the optional template-path input while preserving the existing script.py.mako default; done means revisions can use a shared template location without copying the file into each scripts directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100