[GitHub] [incubator-mxnet] sxjscience commented on pull request #18648: [v1.7.x] Backport some numpy features + fixes

2020-07-01 Thread GitBox
sxjscience commented on pull request #18648: URL: https://github.com/apache/incubator-mxnet/pull/18648#issuecomment-652784885 Close this PR now This is an automated message from the Apache Git Service. To respond to the

[GitHub] [incubator-mxnet] sxjscience commented on pull request #18648: [v1.7.x] Backport some numpy features + fixes

2020-07-01 Thread GitBox
sxjscience commented on pull request #18648: URL: https://github.com/apache/incubator-mxnet/pull/18648#issuecomment-652784828 @ciyongch I'm going to test v1.7 after this backporting PR (https://github.com/apache/incubator-mxnet/pull/18653) is merged. WOuld you merge that one?

[GitHub] [incubator-mxnet] sxjscience commented on pull request #18648: [v1.7.x] Backport some numpy features + fixes

2020-07-01 Thread GitBox
sxjscience commented on pull request #18648: URL: https://github.com/apache/incubator-mxnet/pull/18648#issuecomment-652510821 @sandeep-krishnamurthy @ciyongch I created this PR to track how many numpy commits would potentially go into v1.7.0 (not all of them should go into 1.7.0):

[GitHub] [incubator-mxnet] sxjscience commented on pull request #18648: [v1.7.x] Backport some numpy features + fixes

2020-07-01 Thread GitBox
sxjscience commented on pull request #18648: URL: https://github.com/apache/incubator-mxnet/pull/18648#issuecomment-652295990 In addition, we do have the ability to test whether the numpy APIs are stable or not by checking the tests in GluonNLP:

[GitHub] [incubator-mxnet] sxjscience commented on pull request #18648: [v1.7.x] Backport some numpy features + fixes

2020-07-01 Thread GitBox
sxjscience commented on pull request #18648: URL: https://github.com/apache/incubator-mxnet/pull/18648#issuecomment-652267739 @ciyongch I find that there are lots of numpy stuffs here. This is the initial attempt for backporting some commits. One issue is #17645, in which I'm not sure