Skip to content

Fix simple-to-address typing errors in coordinates - #18695

Merged
nstarman merged 1 commit into
astropy:mainfrom
eerovaher:fewer-coordinates-typing-errors
Nov 29, 2025
Merged

nstarman merged 1 commit into
astropy:mainfrom
eerovaher:fewer-coordinates-typing-errors

Conversation

@eerovaher

Copy link
Copy Markdown
Member

Description

The changes here halve the number of errors Mypy reports if invoked with

mypy --follow-imports silent --exclude tests/ -- astropy/coordinates/

In most cases the cause of the reported error was a missing annotation, which caused Mypy to automatically infer a type that was too narrow. Sometimes the correct place for the annotation was a parent class outside coordinates.

  • By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.

The changes here halve the number of errors Mypy reports if invoked with
`mypy --follow-imports silent --exclude tests/ -- astropy/coordinates/`
In most cases the cause of the reported error was a missing annotation,
which caused Mypy to automatically infer a type that was too narrow.
Sometimes the correct place for the annotation was a parent class
outside `coordinates`.
@eerovaher eerovaher added this to the v7.2.0 milestone Oct 8, 2025
@eerovaher
eerovaher requested a review from mhvk October 8, 2025 16:31
@github-actions

github-actions Bot commented Oct 8, 2025

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
  • Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

@mhvk mhvk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm arguably not the right person to review typing PRs, but this looks good as far as I can tell.

@astrofrog astrofrog modified the milestones: v7.2.0, v8.0.0 Nov 3, 2025
@eerovaher
eerovaher requested a review from nstarman November 28, 2025 14:05

@nstarman nstarman left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@nstarman

Copy link
Copy Markdown
Member

Merging since approved by the relevant maintainer

@nstarman
nstarman merged commit 819c722 into astropy:main Nov 29, 2025
4 checks passed
@eerovaher
eerovaher deleted the fewer-coordinates-typing-errors branch December 1, 2025 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants