| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
This moves the deprecation warning from compile time to runtime.
|
3.14 and 3.13 differ from main, so I would do backporting step by step. |
Sorry, something went wrong.
|
If we can detect this in https://github.com/python/cpython/blob/main/Python/ast_preprocess.c then we get the warning in both static analysis and execution. |
Sorry, something went wrong.
|
Yes, but we only add SyntaxWarning for very common errors. ~True is unlikely used in real code. |
Sorry, something went wrong.
|
Is it hard to detect this in the preprocessor? |
Sorry, something went wrong.
|
I do not know. But even a couple lines of code is a high price for this feature. And it will be more than a couple lines. |
Sorry, something went wrong.
|
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Sorry, something went wrong.
…nt (pythonGH-134982) This moves the deprecation warning from compile time to run time. (cherry picked from commit 86c3316) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
|
GH-136185 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
…nt (pythonGH-134982) This moves the deprecation warning from compile time to run time.
…nt (pythonGH-134982) This moves the deprecation warning from compile time to run time.
…nt (pythonGH-134982) This moves the deprecation warning from compile time to run time.
…nt (pythonGH-134982) This moves the deprecation warning from compile time to run time.
…nt (pythonGH-134982) This moves the deprecation warning from compile time to run time.
| Back | FazBrowse Home | New Git URL |
This moves the deprecation warning from compile time to runtime.