Skip to content

docs: standardize generics spec error labels to 'static error' - #2385

Open
chirag-gupta7 wants to merge 1 commit into
python:mainfrom
chirag-gupta7:fix/2384-generics-error-labels
Open

chirag-gupta7 wants to merge 1 commit into
python:mainfrom
chirag-gupta7:fix/2384-generics-error-labels

Conversation

@chirag-gupta7

@chirag-gupta7 chirag-gupta7 commented Nov 4, 2026 •

Copy link
Copy Markdown

Standardizes error labels in the generics spec to the terse, lowercase static error form suggested in review.

  • Replaces 84 Type checker error labels in docs/spec/generics.rst with static error.

Copilot AI balanced review requested due to automatic review settings November 4, 2026 17:05
@python-cla-bot

python-cla-bot Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

All commit authors signed the Contributor License Agreement.

CLA signed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

@jorenham

jorenham commented Nov 4, 2026

Copy link
Copy Markdown
Collaborator

Standardization makes sense to me, but I personally don't like the verbosity of "Type checker error" here, and would prefer something more terse, and lowercase e.g. "static error".

@chirag-gupta7
chirag-gupta7 force-pushed the fix/2384-generics-error-labels branch from 8d13832 to 9a8cea5 Compare November 4, 2026 17:22
@chirag-gupta7 chirag-gupta7 changed the title docs: standardize generics spec error labels to 'Type checker error' docs: standardize generics spec error labels to 'static error' Nov 4, 2026
@chirag-gupta7

Copy link
Copy Markdown
Author

Did the changes as you suggested @jorenham

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants