-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Unable to specify wheel version for building #11867
Comments
That's the Then, when running I'm not sure this issue is related to Read the Docs, tho. It seems more related to pip/python. If you want to be able to build on Read the Docs, you should probably run
Read more about build customization at https://docs.readthedocs.io/en/latest/build-customization.html Let me know if that helps. |
@humitos Thank you I will look into the pre_install and see if it helps. As a sidenote is there any guide on running readthedocs builds locally? I don't want to spam readthedocs with builds for every small change that may potentially fix an issue that has to do with displaying documentation. I've attempted to docker pull readthedocs builds and tried to get it to build my documentation locally but I have been so far unsuccessful. |
Unfortunately, it's pretty complex and it's not worth the effort.
This is fine, it's not a problem to run build with small changes on Read the Docs 👍🏼 I will close this issue since it seems solved, but feel free to re-open if you are still dealing with it. |
Details
Expected Result
Successfully build with the correct version of wheel being used.
Actual Result
My builds have been recently failing due to a specific library I'm using (mayavi). I've managed to figure out how to get the build to run successfully locally however it still fails when it builds on readthedocs. I've noticed that even when specifying in pyproject.toml
The output logs shows that it is using wheel version 0.40.0:
This confuses me because I thought it did recognize my pyproject.toml:
I'm not quite sure what the exact culprit is but my best guess is that it has to do something with wheel.
The text was updated successfully, but these errors were encountered: