> BTW, there's one thing we've neglected to cover. I was under the impression > that MXNet was using Cython to access the C API for its Python binding, but > it looks like it's using ctypes.
MXNet supports both cython and ctypes (fallback) for the Python interface. It depends on your build configuration. https://github.com/apache/incubator-mxnet/blob/master/CMakeLists.txt#L91 We may want to change the default for MXNet 2 > I don't really want to deal with CI, especially Jenkins, it's a major time > sink and completely unnecessary with services like GitHub Actions these days It's also fine to use Github Actions if that's easier for you. The main reason for using Jenkins is that the MXNet test suite is too large for a free service such as Github Actions and that there are also GPU tests involved. Java tests can initially run on Github Actions and be migrated later to Jenkins based on need. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-mxnet/issues/17783#issuecomment-740674860
