Skip to content

gh-105549: Tokenize separately NUMBER and NAME tokens and allow 0-prefixed literals #105555

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 9, 2023

Conversation

pablogsal
Copy link
Member

@pablogsal pablogsal changed the title Tokenize separately NUMBER and NAME tokens and allow 0-prefixed literals gh-105549: Tokenize separately NUMBER and NAME tokens and allow 0-prefixed literals Jun 9, 2023
@pablogsal pablogsal force-pushed the gh-105549 branch 2 times, most recently from f87ab0d to 58ccc64 Compare June 9, 2023 16:03
@pablogsal pablogsal merged commit b047fa5 into python:main Jun 9, 2023
@pablogsal pablogsal deleted the gh-105549 branch June 9, 2023 20:39
@miss-islington
Copy link
Contributor

Thanks @pablogsal for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jun 9, 2023
… 0-prefixed literals (pythonGH-105555)

(cherry picked from commit b047fa5)

Co-authored-by: Pablo Galindo Salgado <[email protected]>
@bedevere-bot
Copy link

GH-105602 is a backport of this pull request to the 3.12 branch.

@bedevere-bot bedevere-bot removed the needs backport to 3.12 only security fixes label Jun 9, 2023
pablogsal added a commit that referenced this pull request Jun 9, 2023
…w 0-prefixed literals (GH-105555) (#105602)

Co-authored-by: Pablo Galindo Salgado <[email protected]>
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.

6 participants