-
-
Notifications
You must be signed in to change notification settings - Fork 9.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
numpy-1.14.2+mkl-pp3510-pp3510-win32 test errors/failures #10735
Comments
Refcount, npyio and the test_indexing OSError ones are fixed in gh-10737. The unlink failures are because there's no way to close np.memmap on Pypy, except waiting for gc. The docstring-related ones are probably because The test_ctypeslib OSError looks like windows-specific, probably has to do with using the correct platform tag/DLL extension. Probably simple to fix in principle. Not sure about the "No warning raised when calling float64". |
Alternatively it might make sense to move the actual strings into C, like most extension modules do, and remove |
@njsmith Some compilers (MS) also had trouble with long strings, and line breaks were a pain. Creating the docstrings in Python is very convenient, especially if we include utf-8 encoding at some point, so I'd probably be more in favor of generating an include file or writing the interface in Cython. |
Closing. We have PyPy in CI (for linux64). Please reopen/open a new issue if there are still issues with win32 and PyPy, since we don't test that regularily |
Since PyPy compatibility was mentioned in the release announcement for numpy-1.14.2, here are the test errors and failures on PyPy 5.10.1 for Windows:
The text was updated successfully, but these errors were encountered: