-
Notifications
You must be signed in to change notification settings - Fork 28
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
RuntimeError when using numpy <1.13 #57
Comments
It might be like glibc compatibility, so that the compiled version is the oldest supported. That way if we compile with numpy 1.13 the requirement is numpy => 1.13. |
Update: @mwojcikowski compiled rdkit with numpy=1.12, and indeed it works both with 1.12 and 1.13 |
That's strange... the version of the code that I did the conda builds from (the development branch) does actually specify a numpy version: I guess you're on linux? |
Yes, I'm using linux. If I understood correctly, this line: Line 25 in 7e80fec
should be numpy ==1.12 . When its >=1.12, conda can use the most recent version (1.13) to build this package and then it doesn't support the older one (1.12).
Note, that this line: Line 43 in 7e80fec
should stay as it is. |
Got it. Thanks. |
yes, I couldn't test it, but it makes sense to me. I think conda build also supported a specific syntax that was intended to define the runtime requirements based on what was used at build time, but this is also changing a bit in version 3.x, so the proposed constraints should be fine for now. |
Hi,
I have troubles working with the newest version of RDKit together with not-the-newest version of numpy.
It seems like
rdkit
package requiresnumpy=1.13
, although it is not stated in the dependencies. The simplest example that doesn't work (tested on Ubuntu 16.04):and then in Python I get this error:
Note that importing
rdkit
doesn't raise the exception. Also, when I use Python 2.7 I get slightly different error:When I create the environment with numpy v. 1.13 everything works fine (checked in Py3.6 and Py2.7).
The text was updated successfully, but these errors were encountered: