-
Notifications
You must be signed in to change notification settings - Fork 132
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
Add readthedocs config file #276
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jasonpaulos Thanks for catching!
I'll follow up out-of-band to understand how to better monitor the build.
A few thoughts:
- Reading the docs more closely, I see it specifies
.yaml
extension. We previously defined.readthedocs.yml
. Presumably the file extension explains the build failure. - I don't feel strongly about making the change in this PR, but it feels like we ought to delete
.readthedocs.yml
. - Additionally,
.readthedocs.yml
explicitly specifiespython.version: 3.10
. From my read of the docs,build.os.tools
_seems equivalent. Though it feels prudent to set both once the build works (or to make it work).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - (even without the suggested extra line in .readthedocs.yaml
)
Can this yaml file be copied over to the |
Likely yes |
* Add readthedocs config file * Delete old config
Since merging #269, our readthedocs build has failed (as an example, see https://readthedocs.org/projects/pyteal/builds/16635690/), and I believe adding this configuration will properly tell it to use Python 3.10 to build our docs.
If this works, a similar thing will likely need to be added to the Python SDK following algorand/py-algorand-sdk#313 (cc @algochoi)