Fix typos in docstrings (contraint, funciton, priorty)#1808
Merged
CaselIT merged 1 commit intosqlalchemy:mainfrom Apr 20, 2026
Merged
Fix typos in docstrings (contraint, funciton, priorty)#1808CaselIT merged 1 commit intosqlalchemy:mainfrom
CaselIT merged 1 commit intosqlalchemy:mainfrom
Conversation
Member
|
thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repo: sqlalchemy/alembic (⭐ 2700)
Type: docs
Files changed: 4
Lines: +5/-5
What
Corrects three recurring spelling mistakes in user-visible docstrings:
contraint→constraint(3 occurrences acrossop.pyi,operations/base.py,operations/ops.py),funciton→functionandpriorty→priorityinutil/langhelpers.py. Theop.pyistub change matches the autogenerated source so it stays consistent withtools/write_pyi.pyoutput.Why
The misspellings appear in rendered API docs (e.g.
Operations.add_column,PriorityDispatcher) and in IDE tooltips via the.pyistub. Pure documentation polish — no behavior change.Testing
No runtime code paths touched; docstrings only. Verified with
git diffthat only string literals/comments were modified. No need to run the test suite.Risk
Low — docstring/comment-only edits, no functional change.