FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Bug fixes in astropy.visualization.wcsaxes by astrofrog · Pull Request #20221 · astropy/astropy · GitHub

Bug fixes in astropy.visualization.wcsaxes - #20221

Draft
astrofrog wants to merge 22 commits into
astropy:mainfrom
astrofrog:wcsaxes-review-fixes
Draft

Bug fixes in astropy.visualization.wcsaxes#20221
astrofrog wants to merge 22 commits into
astropy:mainfrom
astrofrog:wcsaxes-review-fixes

Conversation

astrofrog commented Aug 6, 2026
edited
Loading

Copy link
Copy Markdown
Member

This PR is the result of an automated review with Claude Opus of the astropy.visualization.wcsaxes submodule. I asked it to keep fixes as simple as possible, keep commit messages concise, and I then reviewed each and every change in detail and iterated on these and dropped some of the fixes. I have included only what I consider non-controversial concise fixes in this PR.

For now I'll keep this as a draft to give me a chance to do another round of review, and to make sure the CI is passing (in particular the image tests). In addition, this will need changelog entries.

So to be clear, the fixes and tests were written by Claude, but I have reviewed every single line and take responsibility for the changes.

  • 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.

github-actions Bot commented Aug 6, 2026

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.

…regexes so malformed formats raise ValueError instead of silently dropping precision
…n one tick label is a prefix of the adjacent one
astrofrog force-pushed the wcsaxes-review-fixes branch from b5b5787 to b529a00 Compare August 6, 2026 23:32
pllim added this to the v8.1.0 milestone Aug 7, 2026
pllim added the Bug label Aug 7, 2026
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants


Back | FazBrowse Home | New Git URL