On Wed, Mar 4, 2015 at 12:33 PM, Guido van Rossum <guido@python.org> 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 ;-)


On Wed, Mar 4, 2015 at 12:23 PM, Brett Cannon <brett@python.org> wrote:

On Wed, Mar 4, 2015 at 3:14 PM Chris Barker <chris.barker@noaa.gov> wrote:
On Tue, Mar 3, 2015 at 8:43 AM, Ethan Furman <ethan@stoneleaf.us> 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 *".


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
Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org

--Guido van Rossum (python.org/~guido)


Christopher Barker, Ph.D.

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