esponsible for them.
>
> Ideally, contributions should follow from a human-to-human discussion in
> the
> form of an issue.
Another point not included here, but we like, is to say that "if you use
AI, you should only submit code which you really understand".
Cheers,
Adrin
On Thu, J
Some historical discussions on a namedarray on the scikit-learn side:
https://github.com/scikit-learn/enhancement_proposals/pull/25
Might be useful to y'all.
On Fri, Oct 20, 2023 at 8:49 AM Dom Grigonis wrote:
> I would make use of it if it was also supporting pure-numpy indices too.
> Pure-num
proposal for a session for the track?
Best,
On Behalf of The EuroScipy Committee,
Adrin
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailm
This discussion and the linked gist may be of some help:
https://github.com/scikit-learn/scikit-learn/issues/11336
On Mon, Nov 22, 2021 at 12:02 PM Andrew Nelson wrote:
> Is there a way to figure out which files are not touched by any open PR?
> That way numpy might be able to do a lot more than
Somewhat relevant, this is the discussion around the same topic we've been
having in scikit-learn:
https://github.com/scikit-learn/enhancement_proposals/pull/30
On Fri, Aug 14, 2020 at 2:36 PM Ilhan Polat wrote:
> Also, not to be a complete slacker, I'd like to add to this list;
>
> - How can I
This somehow also reminds me of the `__array_module__` (NEP37) protocol.
I'm not sure if TF would ever implement it, but it would be really nice if
the NEP37 proposal
would move forward and libraries would implement it.
On Mon, Jun 1, 2020 at 8:22 PM Iordanis Fostiropoulos <
danny.fostiropou...@g
