Avoid leaking module object on numpy C-API import failure

import_array() and import_umath() are macros that expand to `return NULL;`
on failure. When they were called after PyModule_Create(), a failing import
would return directly out of PyInit__ufuncs without releasing the module
object, leaking the strong reference created by PyModule_Create().

Move the imports before the module is created so there is no owned
reference to leak when an import fails.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: antonwolfy

mkl_umath/src/ufuncsmodule.c

@@ -40,6 +40,11 @@ PyMODINIT_FUNC PyInit__ufuncs(void)
     PyObject *m;
     PyObject *d;
 
+    /* import_array()/import_umath() expand to `return NULL;` on failure, so
+     * call them before creating the module object to avoid leaking it. */
+    import_array();
+    import_umath();
+
     m = PyModule_Create(&_ufuncs_module);
     if (m == NULL)
         return NULL;
@@ -50,9 +55,6 @@ PyMODINIT_FUNC PyInit__ufuncs(void)
         return NULL;
     }
 
-    import_array();
-    import_umath();
-
     if (InitOperators(d) < 0) {
         Py_XDECREF(d);
         Py_XDECREF(m);