| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Nice PR! This looks like something that would have had to get approved on Discourse, though.
Sorry, something went wrong.
Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
This is why things get discussed on discourse first 😉 |
Sorry, something went wrong.
There was a problem hiding this comment.
This implementation LGTM.
Although, for core dev review, I'm not too sure about this behavior: if the compiler does not support C11 complex types, then the new format characters are disabled and raise an error with no further information.
I'm worried that this will lead to some bug reports later on wondering why E and C don't work on their system -- it would be ideal to raise a different error mentioning that the system doesn't support C11 (albeit, it would be more work to implement).
Sorry, something went wrong.
There was a problem hiding this comment.
Some minor comments but I also agree that having an error without info for an unknown format if complex are not supported is a bit weird.
Sorry, something went wrong.
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
|
Now on systems without _Complex type - a different error will be raised. |
Sorry, something went wrong.
There was a problem hiding this comment.
On my side it's fine. I didn't check in details the functions bodies, but I assume that the tests should cover most of the cases. I think it remains to wait for Victor's and/or Serhiy's review.
Sorry, something went wrong.
Sorry, something went wrong.
Co-authored-by: Victor Stinner <vstinner@python.org>
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
Merged, thanks. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
📚 Documentation preview 📚: https://cpython-previews--121613.org.readthedocs.build/