GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||
GeezerVison is showing github.com — [3.14] gh-151464: exclude '<>' token from tokenize output (GH-154854) by pablogsal · Pull Request #158190 · python/cpython Conversation
|
|
The required-check aggregate is red because the two Windows ARM jobs fail before compiling CPython: this runner has Visual Studio 18 but lacks the v143 toolset requested by the 3.14 branch. ABI, lint, review gates, and the other required platform jobs passed. The focused tokenizer, syntax, Barry, and future-import suites also pass locally. I am merging this backport with the infrastructure failure noted here. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…onGH-154854) * pythongh-151464: exclude '<>' token from tokenize output Was: ``` $ echo '1 <> 2' | python -m tokenize 1,0-1,1: NUMBER '1' 1,2-1,4: OP '<>' 1,5-1,6: NUMBER '2' 1,6-1,7: NEWLINE '\n' 2,0-2,0: ENDMARKER '' ``` Now (regardless on ``__future__.barry_as_FLUFL`` import): ``` $ echo '1 <> 2' | ./python -m tokenize 1,0-1,1: NUMBER '1' 1,2-1,3: OP '<' 1,3-1,4: OP '>' 1,5-1,6: NUMBER '2' 1,6-1,7: NEWLINE '\n' 2,0-2,0: ENDMARKER '' ``` in accordance with the Grammar: https://docs.python.org/3.14/reference/lexical_analysis.html#operators-and-delimiters Also adds a custom error message for ``<>`` ("not equal" in Pascal and Python 2). * +1 * address review: lowercase and move invalid rule * address review: news * address review: move test_guido_as_bdfl_ineq_tokens() * address review: revert _PyTokenizer_From* changes * + revert unrelated change * address review: remove whatsnew entry (cherry picked from commit 198bc76)
70568b6 to
1ed73a8
Compare
|
The VS 2026 toolset and UWP fixes have now merged in #158188. I rebased this backport onto the updated 3.14 branch, and its checks are running again. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.