apeforest edited a comment on issue #14253: [RFC] Introducing NumPy-compatible
coding experience into MXNet
URL:
https://github.com/apache/incubator-mxnet/issues/14253#issuecomment-468479524
@reminisce I am fine with keeping those two namespaces till 2.0 for backward
compatibility. Starti
apeforest edited a comment on issue #14253: [RFC] Introducing NumPy-compatible
coding experience into MXNet
URL:
https://github.com/apache/incubator-mxnet/issues/14253#issuecomment-468389655
> We can. However, there exist some operators in mxnet.ndarray whose names
are the same as numpy c
apeforest edited a comment on issue #14253: [RFC] Introducing NumPy-compatible
coding experience into MXNet
URL:
https://github.com/apache/incubator-mxnet/issues/14253#issuecomment-468389655
> We can. However, there exist some operators in mxnet.ndarray whose names
are the same as numpy c
apeforest edited a comment on issue #14253: [RFC] Introducing NumPy-compatible
coding experience into MXNet
URL:
https://github.com/apache/incubator-mxnet/issues/14253#issuecomment-467232800
+1 for this RFC.
The inconsistent APIs even within MXNet operators itself caused much
confu
apeforest edited a comment on issue #14253: [RFC] Introducing NumPy-compatible
coding experience into MXNet
URL:
https://github.com/apache/incubator-mxnet/issues/14253#issuecomment-467232800
+1 for this RFC.
The inconsistent APIs even within MXNet operators itself caused much
confu