Send Python-Dev mailing list submissions to
python-dev@python.org
To subscribe or unsubscribe via the World Wide Web, visit
https://mail.python.org/mailman/listinfo/python-dev
or, via email, send a message with subject or body 'help' to
python-dev-request@python.org
You can reach the person managing the list at
python-dev-owner@python.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Python-Dev digest..."
Today's Topics:
1. Re: PEP 485 review (isclose()) (Chris Barker)
2. Re: PEP 485 review (isclose()) (Guido van Rossum)
3. Re: PEP 485 review (isclose()) (Brett Cannon)
4. Re: PEP 485 review (isclose()) (Guido van Rossum)
5. Re: PEP 485 review (isclose()) (Chris Barker)
6. Re: Any volunteers to implement PEP 479? (Guido van Rossum)
7. Re: Any volunteers to implement PEP 479? (Ethan Furman)
----------------------------------------------------------------------
Message: 1
Date: Wed, 4 Mar 2015 12:12:34 -0800
From: Chris Barker <chris.barker@noaa.gov>
To: Ethan Furman <ethan@stoneleaf.us>
Cc: Python Dev <python-dev@python.org>
Subject: Re: [Python-Dev] PEP 485 review (isclose())
Message-ID:
<CALGmxEKSz6wBzq7NyfN9B0S5EBdg3Y9wJttBoBpoebu=8i3jFA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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 *".
>
> +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
Chris.Barker@noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150304/a6ef308b/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 4 Mar 2015 12:22:41 -0800
From: Guido van Rossum <guido@python.org>
To: Chris Barker <chris.barker@noaa.gov>
Cc: Ethan Furman <ethan@stoneleaf.us>, Python Dev
<python-dev@python.org>
Subject: Re: [Python-Dev] PEP 485 review (isclose())
Message-ID:
<CAP7+vJJMxAqG2nuXAXnsFn4+m7N9-0aC4XDe6M07F2-fTNFifw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
No.
On Wed, Mar 4, 2015 at 12:12 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 *".
>>
>> +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
>
> Chris.Barker@noaa.gov
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev@python.org
> 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)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150304/e108818c/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 04 Mar 2015 20:23:24 +0000
From: Brett Cannon <brett@python.org>
To: Chris Barker <chris.barker@noaa.gov>, Ethan Furman
<ethan@stoneleaf.us>
Cc: Python Dev <python-dev@python.org>
Subject: Re: [Python-Dev] PEP 485 review (isclose())
Message-ID:
<CAP1=2W4PZo25prx+U7m4CZX83QD6Qw_K2QEZTkn-WJyaQHevFA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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 *".
>>
>> +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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150304/d2643082/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 4 Mar 2015 12:33:48 -0800
From: Guido van Rossum <guido@python.org>
To: Brett Cannon <brett@python.org>
Cc: Chris Barker <chris.barker@noaa.gov>, Ethan Furman
<ethan@stoneleaf.us>, Python Dev <python-dev@python.org>
Subject: Re: [Python-Dev] PEP 485 review (isclose())
Message-ID:
<CAP7+vJK0h0f=J-DA7hCgom41V+fC=jFc6h0E3-1WoUBeQH-3Qg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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 <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 *".
>>>
>>> +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
> Python-Dev@python.org
> 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)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150304/8a086610/attachment-0001.html>
------------------------------
Message: 5
Date: Wed, 4 Mar 2015 15:26:40 -0800
From: Chris Barker <chris.barker@noaa.gov>
To: Guido van Rossum <guido@python.org>
Cc: Brett Cannon <brett@python.org>, Ethan Furman
<ethan@stoneleaf.us>, Python Dev <python-dev@python.org>
Subject: Re: [Python-Dev] PEP 485 review (isclose())
Message-ID:
<CALGmxE+So8SnybKaEBRpZjos8szrBpsCa3N7HcRusweHsgE_2A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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 ;-)
-Chris
> 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 *".
>>>>
>>>> +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
>> Python-Dev@python.org
>> 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
Chris.Barker@noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150304/10af4471/attachment-0001.html>
------------------------------
Message: 6
Date: Wed, 4 Mar 2015 16:24:39 -0800
From: Guido van Rossum <guido@python.org>
To: Chris Angelico <rosuav@gmail.com>
Cc: Python-Dev <python-dev@python.org>
Subject: Re: [Python-Dev] Any volunteers to implement PEP 479?
Message-ID:
<CAP7+vJJxwJYwCLk4soVbHEi4EC3v1+TfCwP6_b1nWLx==ncUXA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Ping? Anyone? http://bugs.python.org/issue22906
On Fri, Feb 20, 2015 at 9:56 PM, Chris Angelico <rosuav@gmail.com> wrote:
> On Wed, Jan 7, 2015 at 2:48 PM, Guido van Rossum <guido@python.org> 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
> Python-Dev@python.org
> 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)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150304/57d420cc/attachment-0001.html>
------------------------------
Message: 7
Date: Wed, 04 Mar 2015 16:42:15 -0800
From: Ethan Furman <ethan@stoneleaf.us>
To: python-dev@python.org
Subject: Re: [Python-Dev] Any volunteers to implement PEP 479?
Message-ID: <54F7A667.4050205@stoneleaf.us>
Content-Type: text/plain; charset="iso-8859-1"
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~
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150304/96c32fd5/attachment-0001.sig>
------------------------------
Subject: Digest Footer
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
------------------------------
End of Python-Dev Digest, Vol 140, Issue 6
******************************************