Re: [Python-Dev] PEP 485 review (isclose())
On Tue, Mar 3, 2015 at 8:43 AM, Ethan Furman wrote: > On 03/03/2015 01:17 AM, Victor Stinner wrote: > > > Maybe it's time to rename the math module to _math and create a > > math.py module, like _decimal/decimal? math.py should end with "from > > _math import *". > > +1 > What do folks think? If we're going to do this, I'll write isclose() in python. And I could do the work to split it out, too, I suppose. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R(206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [email protected] ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 485 review (isclose())
On Wed, Mar 4, 2015 at 3:14 PM Chris Barker wrote: > On Tue, Mar 3, 2015 at 8:43 AM, Ethan Furman wrote: > >> On 03/03/2015 01:17 AM, Victor Stinner wrote: >> > > >> > Maybe it's time to rename the math module to _math and create a >> > math.py module, like _decimal/decimal? math.py should end with "from >> > _math import *". >> >> +1 >> > > What do folks think? If we're going to do this, I'll write isclose() in > python. And I could do the work to split it out, too, I suppose. > My vote -- as always -- is to do it in Python. If someone is sufficiently motivated to re-implement in C then that's great, but I don't think it should be required to be in C. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 485 review (isclose())
No. On Wed, Mar 4, 2015 at 12:12 PM, Chris Barker wrote: > On Tue, Mar 3, 2015 at 8:43 AM, Ethan Furman wrote: > >> On 03/03/2015 01:17 AM, Victor Stinner wrote: >> > > >> > Maybe it's time to rename the math module to _math and create a >> > math.py module, like _decimal/decimal? math.py should end with "from >> > _math import *". >> >> +1 >> > > What do folks think? If we're going to do this, I'll write isclose() in > python. And I could do the work to split it out, too, I suppose. > > -Chris > > > > > > -- > > Christopher Barker, Ph.D. > Oceanographer > > Emergency Response Division > NOAA/NOS/OR&R(206) 526-6959 voice > 7600 Sand Point Way NE (206) 526-6329 fax > Seattle, WA 98115 (206) 526-6317 main reception > > [email protected] > > ___ > Python-Dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/guido%40python.org > > -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 485 review (isclose())
In this case I disagree. The math module mostly wraps the C math library and the bar should remain high for things to be added to it. Let this be someone's opportunity to learn C (I guess not Chris's :-). On Wed, Mar 4, 2015 at 12:23 PM, Brett Cannon wrote: > > > On Wed, Mar 4, 2015 at 3:14 PM Chris Barker wrote: > >> On Tue, Mar 3, 2015 at 8:43 AM, Ethan Furman wrote: >> >>> On 03/03/2015 01:17 AM, Victor Stinner wrote: >>> >> >> >>> > Maybe it's time to rename the math module to _math and create a >>> > math.py module, like _decimal/decimal? math.py should end with "from >>> > _math import *". >>> >>> +1 >>> >> >> What do folks think? If we're going to do this, I'll write isclose() in >> python. And I could do the work to split it out, too, I suppose. >> > > My vote -- as always -- is to do it in Python. If someone is sufficiently > motivated to re-implement in C then that's great, but I don't think it > should be required to be in C. > > ___ > Python-Dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/guido%40python.org > > -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 485 review (isclose())
On Wed, Mar 4, 2015 at 12:33 PM, Guido van Rossum wrote: > In this case I disagree. The math module mostly wraps the C math library > and the bar should remain high for things to be added to it. Let this be > someone's opportunity to learn C (I guess not Chris's :-). > As it happens, the first C code I ever wrote, beyond toy examples, was python extensions. I dropped that for Cython a good while ago, but I can remember enough for this simple function ;-) I agree that it's not worth going to python for the math module for just this -- but others were proposing other reasons to do it. Back to look at K&R ;-) -Chris > On Wed, Mar 4, 2015 at 12:23 PM, Brett Cannon wrote: > >> >> >> On Wed, Mar 4, 2015 at 3:14 PM Chris Barker >> wrote: >> >>> On Tue, Mar 3, 2015 at 8:43 AM, Ethan Furman wrote: >>> On 03/03/2015 01:17 AM, Victor Stinner wrote: >>> >>> > Maybe it's time to rename the math module to _math and create a > math.py module, like _decimal/decimal? math.py should end with "from > _math import *". +1 >>> >>> What do folks think? If we're going to do this, I'll write isclose() in >>> python. And I could do the work to split it out, too, I suppose. >>> >> >> My vote -- as always -- is to do it in Python. If someone is sufficiently >> motivated to re-implement in C then that's great, but I don't think it >> should be required to be in C. >> >> ___ >> Python-Dev mailing list >> [email protected] >> https://mail.python.org/mailman/listinfo/python-dev >> Unsubscribe: >> https://mail.python.org/mailman/options/python-dev/guido%40python.org >> >> > > > -- > --Guido van Rossum (python.org/~guido) > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R(206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [email protected] ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Any volunteers to implement PEP 479?
Ping? Anyone? http://bugs.python.org/issue22906 On Fri, Feb 20, 2015 at 9:56 PM, Chris Angelico wrote: > On Wed, Jan 7, 2015 at 2:48 PM, Guido van Rossum wrote: > > There's a proof of concept patch in http://bugs.python.org/issue22906, > but > > it doesn't have the __future__ import and probably gets other details > wrong. > > > > Reference: > > PEP 479 -- Change StopIteration handling inside generators > > > > -- > > --Guido van Rossum (python.org/~guido) > > For the benefit of people who haven't been following the tracker > issue: There is now a patch which *does* create the __future__ > directive and so on. It applies cleanly to current tip (I just tested > it again today), and the test suite passes on Debian AMD64. Can other > people please try this, on other platforms, and see how it goes? > > ChrisA > ___ > Python-Dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Any volunteers to implement PEP 479?
On 03/04/2015 04:24 PM, Guido van Rossum wrote: > > Ping? Anyone? http://bugs.python.org/issue22906 Running tests on an ubuntu system... -- ~Ethan~ signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
