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 time -- so we compromised on having the whole thing enabled through `#ifdef`. Clearly it started rotting the day I committed the code...
On Mon, Jan 2, 2017 at 4:22 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > On 2 January 2017 at 18:27, Nathaniel Smith <n...@pobox.com> 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 warning in the docs and the fact it's apparently been > fundamentally broken for years is sufficient justification for just > dropping it entirely. An explicit deprecation warning could be added in > 3.6.1 and a Py3k warning in 2.7.x, though - those changes shouldn't be > difficult, and it's a nice courtesy for anyone that *is* somehow currently > getting it to work. > > Cheers, > Nick. > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia > > _______________________________________________ > 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)
_______________________________________________ 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/archive%40mail-archive.com
