-
-
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
Build Failed. TypeError: 'generator' object is not subscriptable #8616
Comments
The version of The build that passed installed |
@humitos thank you |
For future readers, the solution for this problem is to pin
More information in our docs. See also our page on reproducible builds to better understand how to use requirements files on Read the Docs. |
A recent update in docutils breaks builds on readthedocs. This is the suggested work around from readthedocs [1]. [1] - readthedocs/readthedocs.org#8616
Great summary originally posted by @joshuacwnewton in sphinx-doc/sphinx#9783 (comment):
|
Quick addendum:
I've seen this trip up projects where folks were already pinning Sphinx, only to find out that RTD wasn't picking up those extra requirements. |
Fix issue where Sphinx doesn't work with docutils 0.18 by specifying a version constraint in docs/requirements.txt. More details: readthedocs/readthedocs.org#8616
Fix issue where Sphinx doesn't work with docutils 0.18 by specifying a version constraint in docs/requirements.txt. More details: readthedocs/readthedocs.org#8616
A recent update in docutils breaks builds on readthedocs. This is the suggested work around from readthedocs [1]. [1] - readthedocs/readthedocs.org#8616
The newest version of docutils clashes with the built system in readthedocs. An older version is required for it to work. See readthedocs/readthedocs.org#8616
Update: Sphinx 1.8.6 was released this week, and it pins docutils to However, users of old pip versions (for example on Python 2) might not benefit from this, and will need to pin docutils themselves anyway. Otherwise, they will still observe the error, plus this warning on the logs:
|
Am 19.11.21 schrieb Juan Luis Cano Rodríguez:
However, users of old pip versions (for example on Python 2) might not
benefit from this
...
Could you test whether Docutils 0.18.1b (released on Thursday) fixes the
error? Then, Sphinx 1.8.x could lift the pin to `docutils < 1.0`.
|
Thanks @gmilde , looking into this 👍🏽 |
@gmilde I confirm that docutils 0.18.1b1 does not exhibit the I was testing with a fork of the project where I originally detected this. I may delete the project at any time.
Amending diff: astrojuanlu/phpunit-documentation-english@968e3d2 |
Add readthedocs.yaml Add requirements with docutils<0.18 (described in readthedocs/readthedocs.org#8616)
* link docs and add badge to readme * add workaround for docutils problem readthedocs/readthedocs.org#8616 * update copyright * move toc to intro page * delete old index before moving intro in its place * move intro into index's place * fix path * fix another path
...as pinning `docutils<0.18` seems no longer necessary (see: readthedocs/readthedocs.org#8616).
Upstream cause is at readthedocs/readthedocs.org#8616 (comment) The solution is at readthedocs/readthedocs.org#8616 (comment)
Update from @astrojuanlu: see this comment for a workaround for this issue, our blog for a more detailed explanation, and this comment for current status of this issue
Success Build: https://readthedocs.org/projects/diadocsdk-1c/builds/15092197/
Failed Build: https://readthedocs.org/projects/diadocsdk-1c/builds/15095749/
It's the same commit
What is changed during 8 hours ?
What can I do for successful build?
The text was updated successfully, but these errors were encountered: