On Sun, Dec 25, 2016 at 5:55 PM, Nick Coghlan wrote:
> On 25 December 2016 at 09:48, Nathaniel Smith wrote:
>>
>> Or maybe make it so that even no-fpectl builds still export the
>> necessary symbols so that yes-fpectl extensions don't crash on import?
>> (This has the advantage that it can be don
On 2 January 2017 at 18:27, Nathaniel Smith wrote:
> So I guess that yeah, my suggestion would be to drop this feature
> entirely in 3.7, given that it's never been enabled by default and has
> been largely broken for years. Or do we still need a full deprecation
> cycle?
>
I think the existing
I am happy to see it go. It was contributed many, many years ago by people
(scientists from the early numpy world IIRC) who had a very specific use
for it, but weren't really into maintaining it long-term, and I wasn't
strong enough to refuse a well-meaning but poorly executed contribution at
the t
Great, sounds like we have a plan: https://bugs.python.org/issue29137
On Mon, Jan 2, 2017 at 8:21 AM, Guido van Rossum wrote:
> I am happy to see it go. It was contributed many, many years ago by people
> (scientists from the early numpy world IIRC) who had a very specific use for
> it, but weren
On behalf of the Python development community and the Python 3.4 and
Python 3.5 release teams, I'm pleased to announce the availability of
Python 3.4.6rc1 and Python 3.5.6rc1.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. Python 3.4 now
