Skip to content

Build failing for project with matplotlib dependencies (I believe I have read every solution - HALP! 🙏) #1671

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

Closed
drvinceknight opened this issue Sep 21, 2015 · 8 comments
Labels
Support Support question

Comments

@drvinceknight
Copy link

On a library that makes use of matplotlib (and also numpy) we only just noticed a failed build. In fact the docs stopped building in mid August 😢 but the first failing commit didn't really have anything in it that changed the docs.

You can see the issue here: Axelrod-Python/Axelrod#318 which has more information.

I have tried:

I have tried a large number of changes without any luck (a co contributor and I spent pretty much all afternoon committing and reverting every single thing we could find/think off).

Ultimately I would be happy if it were possible to build the documentation without building the library at all (I think that I need to disable autodoc for that which I have also tried)...

Here is the conf.py file for the repo (on branch 318 which is being built by rtd): https://github.com/Axelrod-Python/Axelrod/blob/318/docs/conf.py

Any explanation and/or pointers would be appreciated.

@drvinceknight
Copy link
Author

I have also tried the solutions helpfully suggested at #1624.

@capcarr
Copy link

capcarr commented Sep 22, 2015

I noticed that your setup.py file includes matplotlib in the install_requires keyword. This will probably break the installation process, but have you tried building the docs without this?

@meatballs
Copy link

The last successful build (3259753) was on August 20th at commit 67491390f6edb9e91cec2e3d04e66712924fa7bb

I've now created a 'docstest' branch at that commit and triggered build 3342236. It fails with the same error we've seen since August 20th.

@meatballs
Copy link

@capcarr thanks for the suggestion. I just tried it on build #3342348, but it made no difference.

@capcarr
Copy link

capcarr commented Sep 22, 2015

@meatballs Even when specifying an empty requirements file on RTD?

@meatballs
Copy link

Aha! I removed install_requires and then used the advanced options to use virtualenv and an empty requirements.txt created in the docs folder. It built!!

Doesn't really explain why it should suddenly have stopped, though.

@meatballs
Copy link

Is this related to commit d36ebae which is dated August 20th - the last time our docs built?

I can see it contains a change to tasks.py (line 312) that seems relevant here.

@gregmuellegger
Copy link
Contributor

I'm not sure if the mentioned commit is source of the problems you have experienced. But cool that you were able to resolve the issue. The real problem here is that we cannot support installing custom versions of matplotlib (all the nasty compiling involved .. 😞) so a build will fail if matplotlib is mentioned in a requirements file or in the install_requires option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Support Support question
Projects
None yet
Development

No branches or pull requests

4 participants