Skip to content

Refactor check_token to improve performance by replacing regex with a simple Python function - #20439

Open
hamogu wants to merge 1 commit into
astropy:mainfrom
hamogu:fix_regex
Open

hamogu wants to merge 1 commit into
astropy:mainfrom
hamogu:fix_regex

Conversation

@hamogu

@hamogu hamogu commented Sep 18, 2026

Copy link
Copy Markdown
Member

Description

This pull request replaces a regex with a simple Python function to avoid the regex loosing performance as it backtrachs through the capture groups.

AI disclosure

I used an LLM to help me understand the older regexp initially, but found that more traditional tools like regexp101.com actually helped me more.

  • 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 github-actions Bot added the utils label Sep 18, 2026
@github-actions

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.

@pllim pllim added this to the v8.1.0 milestone Sep 18, 2026
@@ -0,0 +1 @@
Replace regexp that can get bogged down in backtracking with simply Python function.

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.

Suggested change
Replace regexp that can get bogged down in backtracking with simply Python function.
Replace regexp that can get bogged down in backtracking with simple Python comparisons.

@pllim

pllim commented Sep 18, 2026

Copy link
Copy Markdown
Member

I will just have to trust you and the CI on this one. Just a small comment on change log verbiage. Would be nice if others well-versed in regex could have a look too. @jdavies-st , I remember you loved regex...

@jdavies-st

jdavies-st commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Would be nice if others well-versed in regex could have a look too. @jdavies-st , I remember you loved regex...

Loved is a bit strong. I do love https://regex101.com so I don't have to think too hard about them myself. 🧠 🚑

I'll have a look.

@pllim
pllim requested a review from jdavies-st September 18, 2026 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants