8000 bpo-43833: Emit warnings for numeric literals followed by keyword by serhiy-storchaka · Pull Request #25466 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

bpo-43833: Emit warnings for numeric literals followed by keyword #25466

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.

Sign up for GitHub

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 4 commits into from
Jun 8, 2021
Merged

bpo-43833: Emit warnings for numeric literals followed by keyword #25466

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
56ae489
bpo-43833: Emit warnings for numeric literals followed by keyword
serhiy-storchaka Apr 18, 2021
7185f45
Improve comment.
serhiy-storchaka Apr 18, 2021
7caff32
Merge branch 'main' into end-of-numeric-literal
serhiy-storchaka May 16, 2021
f9ffba0
Update Doc/whatsnew/3.10.rst
pablogsal Jun 8, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update Doc/whatsnew/3.10.rst
  • Loading branch information
@pablogsal
pablogsal authored Jun 8, 2021
commit f9ffba0751422c12edfbb11a1a8918a8a60d197f
6 changes: 3 additions & 3 deletions Doc/whatsnew/3.10.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1649,9 +1649,9 @@ that may require changes to your code.
Changes in the Python syntax
----------------------------

* Deprecation warning is now emitted when compile previously valid syntax
if the numeric literal is immediately followed by keyword (like in ``0in x``).
If future releases it will be changed to syntax warning, and finally to
* Deprecation warning is now emitted when compiling previously valid syntax
if the numeric literal is immediately followed by a keyword (like in ``0in x``).
If future releases it will be changed to syntax warning, and finally to a
syntax error. To get rid of the warning and make the code compatible with
future releases just add a space between the numeric literal and the
following keyword.
Expand Down
0