Howdy howdy. It's-a me, Larry, your friendly neighborhood Python 3.5
Release Manager.
Somewhere around 2 or 3pm tomorrow I expect to tag Python 3.5 beta 1.
We'll actually release beta 1 on Sunday, once the binary installers are
all built.
Beta 1 is also feature-freeze, meaning no new fe
Is it too late to get the isclose() code (PEP 485) into 3.5?
I posted the code here, and got a tiny bit of review, but have not yet
merged it into the source tree -- and don't know the process for getting it
committed to the official source.
So -- too late, or should I try to get that merge done
On 05/22/2015 02:29 PM, Chris Barker wrote:
Is it too late to get the isclose() code (PEP 485) into 3.5?
I posted the code here, and got a tiny bit of review, but have not yet
merged it into the source tree -- and don't know the process for
getting it committed to the official source.
So --
On Fri, May 22, 2015 at 2:33 PM, Larry Hastings wrote:
> On 05/22/2015 02:29 PM, Chris Barker wrote:
>
> Is it too late to get the isclose() code (PEP 485) into 3.5?
>
> ...
> Hopefully you can find a core dev familiar enough with the issues
> involved that they can (quickly!) guide it throug
On Sat, May 23, 2015 at 12:53 AM, Chris Barker wrote:
> On Fri, May 22, 2015 at 2:33 PM, Larry Hastings wrote:
>>
>> On 05/22/2015 02:29 PM, Chris Barker wrote:
>>
>> Is it too late to get the isclose() code (PEP 485) into 3.5?
>
> ...
>>
>> Hopefully you can find a core dev familiar enough wit
