-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
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
bpo-43521: Allow ast.unparse with empty sets and NaN #24897
bpo-43521: Allow ast.unparse with empty sets and NaN #24897
Conversation
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
Thanks for the fix @Kodiologist! |
Lib/ast.py
Outdated
else: | ||
# `{}` would be interpreted as a dictionary literal, and | ||
# `set` might not be shadowed. Thus: | ||
self.write('{1}.__class__()') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps {*()}
would be a bit more concise?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, the {1}
can be a bit confusing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just for the reference, the proposed was is how astor does it. Though I think {*()}
is also a good alternative
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, I'm the one who wrote that astor patch. I didn't realize {*()}
was a possibility.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
< joking>
What about this nuclear option?
>>> ctypes.pythonapi.PySet_New.argtypes = ctypes.py_object,
>>> ctypes.pythonapi.PySet_New.restype = ctypes.py_object
>>> ctypes.pythonapi.PySet_New([]).__class__
<class 'set'>
< /joking>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall it looks fine to me. One little nit is that, can you please adjust your style (like end parens on different lines) to match with the other parts of the code?
E.g;
self.write(
repr(value)
.replace("inf", _INFSTR)
.replace("nan", "({}-{})".format(_INFSTR, _INFSTR))
)
(same goes for the tests)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, but I'm not an expert in this module. @pablogsal should probably take a look at it.
ec165a0
to
9cbd740
Compare
Looks fantastic. @Kodiologist could you also add a NEWS entry using |
9cbd740
to
d811584
Compare
Thanks, done. |
Also, no need to force-push. The commits will be squashed anyways when your patch is merged. (I find it's better to keep a full commit history here, since it gives context to the discussions if we need to come back to this later.) |
I plan to backport this because I consider it close enough to the "bug" territory (although is within the initial design constraints). If someone disagrees, please, express yourself and we can remove the label. |
Is automerge stuck? |
Thanks @Kodiologist for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9. |
GH-24921 is a backport of this pull request to the 3.9 branch. |
Automerge-Triggered-By: GH:pablogsal (cherry picked from commit 08ff436) Co-authored-by: Kodi Arfer <Kodiologist@users.noreply.github.com>
Ah, I had to use https://check-python-cla.herokuapp.com to get the bots to notice that I'd signed the CLA. |
* master: (129 commits) bpo-43452: Micro-optimizations to PyType_Lookup (pythonGH-24804) bpo-43517: Fix false positive in detection of circular imports (python#24895) bpo-43494: Make some minor changes to lnotab notes (pythonGH-24861) Mention that code.co_lnotab is deprecated in what's new for 3.10. (python#24902) bpo-43244: Remove symtable.h header file (pythonGH-24910) bpo-43466: Add --with-openssl-rpath configure option (pythonGH-24820) Fix a typo in c-analyzer (pythonGH-24468) bpo-41561: Add workaround for Ubuntu's custom security level (pythonGH-24915) bpo-43521: Allow ast.unparse with empty sets and NaN (pythonGH-24897) bpo-43244: Remove the PyAST_Validate() function (pythonGH-24911) bpo-43541: Fix PyEval_EvalCodeEx() regression (pythonGH-24918) bpo-43244: Fix test_peg_generators on Windows (pythonGH-24913) bpo-39342: Expose X509_V_FLAG_ALLOW_PROXY_CERTS in ssl module (pythonGH-18011) bpo-43244: Fix test_peg_generator for PyAST_Validate() (pythonGH-24912) bpo-42128: Add 'missing :' syntax error message to match statements (pythonGH-24733) bpo-43244: Add pycore_ast.h header file (pythonGH-24908) bpo-43244: Rename pycore_ast.h to pycore_ast_state.h (pythonGH-24907) Remove unnecessary imports in the grammar parser (pythonGH-24904) bpo-35883: Py_DecodeLocale() escapes invalid Unicode characters (pythonGH-24843) Add PEP 626 to what's new in 3.10. (python#24892) ...
https://bugs.python.org/issue43521
Automerge-Triggered-By: GH:pablogsal