[Numpy-discussion] Proposal to accept NEP-18, array_function protocol (original) (raw)
Hameer Abbasi einstein.edison at gmail.com
Fri Aug 24 04:34:07 EDT 2018
- Previous message (by thread): [Numpy-discussion] Proposal to accept NEP-18, __array_function__ protocol
- Next message (by thread): [Numpy-discussion] Proposal to accept NEP-18, __array_function__ protocol
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi everyone,
On Fri, Aug 24, 2018 at 9:38 AM Nathaniel Smith <njs at pobox.com> wrote:
On Thu, Aug 23, 2018 at 9:02 AM, <einstein.edison at gmail.com> wrote: > I might add that most duck array authors are highly unlikely to be newcomers > to the Python space. We should just put a big warning there while enabling > and that’ll be enough to scare away most devs from doing it by default.
That's a reasonable idea... a Big Obnoxious Warning(tm) when it's enabled, or on first use, would achieve a lot of the same purpose. E.g. if thisisthefirstarrayfunctionusage(): sys.stderr.write( "WARNING: this program uses NumPy's experimental 'arrayfunction' feature.\n" "It may change or be removed without warning, which might break this program.\n" "For details see http://www.numpy.org/neps/nep-0018-array-function-protocol.html\n" ) -n I was thinking of a FutureWarning... That's essentially what it's for. Writing to stderr looks un-pythonic to me.
-- Nathaniel J. Smith -- https://vorpus.org
NumPy-Discussion mailing list NumPy-Discussion at python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Best Regards, Hameer Abbasi -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20180824/2dee0339/attachment-0001.html>
- Previous message (by thread): [Numpy-discussion] Proposal to accept NEP-18, __array_function__ protocol
- Next message (by thread): [Numpy-discussion] Proposal to accept NEP-18, __array_function__ protocol
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]