[GitHub] [incubator-mxnet] reminisce commented on issue #16370: Disable Pylint false error in numpy_op_signature

2019-10-04 Thread GitBox
reminisce commented on issue #16370: Disable Pylint false error in numpy_op_signature URL: https://github.com/apache/incubator-mxnet/pull/16370#issuecomment-538542126 @marcoabreu `from __future__ import absolute_import` is used almost everywhere throughout the code base. And please read

[GitHub] [incubator-mxnet] reminisce commented on issue #16370: Disable Pylint false error in numpy_op_signature

2019-10-03 Thread GitBox
reminisce commented on issue #16370: Disable Pylint false error in numpy_op_signature URL: https://github.com/apache/incubator-mxnet/pull/16370#issuecomment-538176570 Another proof for why `absolute_import` is required in python2. If that were deleted, and you typed `import numpy` in

[GitHub] [incubator-mxnet] reminisce commented on issue #16370: Disable Pylint false error in numpy_op_signature

2019-10-03 Thread GitBox
reminisce commented on issue #16370: Disable Pylint false error in numpy_op_signature URL: https://github.com/apache/incubator-mxnet/pull/16370#issuecomment-538172017 @marcoabreu Could you explain why it didn't error out for many PRs after `numpy_op_signature.py` was introduced? The