Thanks for the feedback!Created PR for adding both einops and opt_einsum:https://github.com/numpy/numpy/pull/17432 27.09.2020, 12:30, "Ralf Gommers" : On Sun, Sep 27, 2020 at 7:09 AM Stephan Hoyer <sho...@gmail.com> wrote:On Sat, Sep 26, 2020 at 10:53 PM Alex Rogozhniko
Hello all, I'm developer of einops - python package for readable and reliable tensor operations.Einops handles different types of tensors (including numpy, pytorch, jax, tensorflow and others) and targeted as a verbose replacement to existing numpy operations. As einops now is quite mature project,
oss a set of popular tensor packages. It should also complement well existing deep learning packages when operations are missingor when extensive usage of transpose/reshapes/broadcasts drives to hardly readable and (frequently) buggy code. Would be happy to hear feedback. Regards,Alex Rogozhnikov Pr
o this, some of which has been outlined by Nathaniel, and the rest I have an outline for how to implement. I can advise someone on how to do this. -TravisOn Thu, Oct 25, 2018 at 3:17 PM Alex Rogozhnikov <alex.rogozhni...@yandex.ru> wrote:Dear numpy community, I'm planning to dep
The conservative way to handle this would be to do a deprecation cycle, specifically by issuing FutureWarning when scalars or 0d arrays are encountered as inputs.Sounds good to me. Behavior should be scheduled for numpy 1.18? 26.10.2018, 05:02, "Stephan Hoyer" :On Thu, Oct 25, 2018 at 3:10 PM An
;not arrays". Please see original discussion at github for more detailshttps://github.com/numpy/numpy/issues/5300 Your comments welcome,Alex Rogozhnikov ___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
