| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Simply comment out the test. |
Sorry, something went wrong.
This reverts commit 9c29e17.
There was a problem hiding this comment.
LGTM. 👍
Sorry, something went wrong.
|
Thanks @StanFromIreland for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14, 3.15. |
Sorry, something went wrong.
|
Sorry, @StanFromIreland, I could not cleanly backport this to 3.14 due to a conflict. cherry_picker 8477652cc122e744bcc70c1e133905bcbe2d8516 3.14 |
Sorry, something went wrong.
|
GH-153204 is a backport of this pull request to the 3.15 branch. |
Sorry, something went wrong.
|
Sorry, @StanFromIreland, I could not cleanly backport this to 3.13 due to a conflict. cherry_picker 8477652cc122e744bcc70c1e133905bcbe2d8516 3.13 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This is technically disallowed by the documentation of PyBytes_DecodeEscape (added in 37e2762), which says:
However, this was triggered by our test suite, which explicitly tests this case:
cpython/Lib/test/test_capi/test_bytes.py
Line 225 in 9c29e17
Should we also update the documentation? CC @ZeroIntensity (added docs) and @serhiy-storchaka (added test)