-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
gh-90568: Fix error type when parse \N with a named sequence in RE #91665
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
gh-90568: Fix error type when parse \N with a named sequence in RE #91665
Conversation
re.error is now raised instead of TypeError.
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9, 3.10. |
Sorry, @serhiy-storchaka, I could not cleanly backport this to |
Sorry @serhiy-storchaka, I had trouble checking out the |
…e in RE (pythonGH-91665) re.error is now raised instead of TypeError.. (cherry picked from commit 6ccfa31) Co-authored-by: Serhiy Storchaka <[email protected]>
GH-91830 is a backport of this pull request to the 3.10 branch. |
… in RE (pythonGH-91665) (pythonGH-91830) (pythonGH-91834) re.error is now raised instead of TypeError. (cherry picked from commit 6ccfa31) (cherry picked from commit 9c18d78) Co-authored-by: Serhiy Storchaka <[email protected]>
re.error is now raised instead of TypeError.
Closes #90568.