-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Unable to build project with numpy #1624
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
Comments
I can replicate the issue locally with Closing as this isn't a Read the Docs issue. |
OK, thanks. Can you suggest any workarounds in the mean time? |
Try a standard |
For future reference, I was only able to build my documentation by specifying an empty requirements file in RTD Admin, and by mocking any 3rd party packages in |
I tried this approach (and a large number of others) for #1671 but without any success. |
What settings are you using in RTD? I have these checked, under the Advanced Settings:
And the requirements file is pointing to an empty file (actually two empty lines). In the
|
I've tried that (I've been going through every single solution and permutation thereof I kind find). I've opened another issue #1671 in the hope of figuring this out (another core dev and I spent about 4 hours trying to fix this today). Not sure if this is of interest but here's the build log: https://readthedocs.org/projects/axelrod/builds/3340162/ and here's a pic of my (latest) settings: https://www.dropbox.com/s/9ua3xq2ww8165y9/Screenshot%202015-09-21%2018.26.56.png?dl=0 for that my latest build failed with this mock in the conf (I copied exactly yours and added some matplotlib sub libraries, and then just had the ones I use: no difference all failed):
I have also removed all uses of |
I'm unable to build the documentation for my project, which depends on numpy (and scipy and matplotlib). The build fails with a RequirementParseError for numpy. Here's the log: https://readthedocs.org/projects/biosppy/builds/3295858/
Under Admin->Advanced Settings I have both the options "Install your project inside a virtualenv using setup.py install" and "Give the virtual environment access to the global site-packages dir." checked.
The text was updated successfully, but these errors were encountered: