The discussion on this list is plenty. Just write the PEP! On Wed, Sep 9, 2020 at 12:07 PM Cade Brown <brown.c...@gmail.com> wrote:
> All, > > For reference, my PEP repo: https://github.com/CadeBrown/peps > > > Guido, > > Thanks for helping out. And yes I'd be interested in writing a PEP. I'm > forking the repository (as mentioned above in my message). Where should > discussion specific to the PEP take place? Should we move to 1-on-1 email > conversations, or should it be kept in the public mailing list? > > Thanks, > ---- > *Cade Brown* > Research Assistant @ ICL (Innovative Computing Laboratory) > Personal Email: brown.c...@gmail.com > ICL/College Email: c...@utk.edu > > > > > On Tue, Sep 8, 2020 at 11:48 PM Guido van Rossum <gu...@python.org> wrote: > >> If you and Cade want to co-author a PEP that adds `inf` and `nan` to the >> builtins, I'll sponsor it, so you can have a fair hearing from the SC. I >> won't argue in favor, but not against either.) >> >> On Tue, Sep 8, 2020 at 6:26 PM Christopher Barker <python...@gmail.com> >> wrote: >> >>> Thanks Jon and Chris. But I'm not looking to make a literal_eval or >>> custom reprs that support inf and nan -- I may need that some day, so >>> thanks for the tips, but the idea here is to do that little bit more to >>> make Python better support the float special values out of the box. >>> >>> It seems that moving math,inf and math.nan to __builtins__, and adding >>> them to a "whitelist" in literal_eval (and maybe another place or two?) >>> would accomplish this. Small benefit, yes, but I have yet to hear anyone >>> present a downside (other than the usual it's work that someone has to do). >>> >>> I took another look at PEP 754 (which was rejected due to disinterest, >>> not because it was determined to be a bad idea), and note that the only >>> part that wasn't implemented was the creation of "constants" in >>> __builtins__ (and, indeed, the PEP is not clear on whether it was >>> suggesting that they be in __builtins__ at all). The PEP also called for >>> different names, and a constant for negative Infinity, which doesn't seem >>> very useful when you can just use a negative sign. >>> >>> Anyway, I'm done now -- there hasn't been any interest from core devs, >>> and I don't care enough to push this, but it would be nice. >>> >>> -CHB >>> >>> >>> -- >>> Christopher Barker, PhD >>> >>> Python Language Consulting >>> - Teaching >>> - Scientific Software Development >>> - Desktop GUI and Web Development >>> - wxPython, numpy, scipy, Cython >>> _______________________________________________ >>> Python-ideas mailing list -- python-ideas@python.org >>> To unsubscribe send an email to python-ideas-le...@python.org >>> https://mail.python.org/mailman3/lists/python-ideas.python.org/ >>> Message archived at >>> https://mail.python.org/archives/list/python-ideas@python.org/message/4VK6ND3GURQHSXZWHKBX43WOKOOUFRP5/ >>> Code of Conduct: http://python.org/psf/codeofconduct/ >>> >> >> >> -- >> --Guido van Rossum (python.org/~guido) >> *Pronouns: he/him **(why is my pronoun here?)* >> <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/> >> > -- --Guido van Rossum (python.org/~guido) *Pronouns: he/him **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/RCFC6TLYRBBSXUBKBODPH3G6SQOOLJ2B/ Code of Conduct: http://python.org/psf/codeofconduct/
