-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Issue with intersphinx with latest developer version of Sphinx #3234
Comments
At my local, I can't reproduce the problem. With sphinx-1.5:
With master HEAD:
Note: my settings
|
Note: The reported warnings came from some ValueError on
To investigate more deeply, we have to know what exception did |
Finally, I updated error message to investigate the error at 4047329. @astrofrog Could you try this please? |
I have the same problem:
Seems like requests does not handle gzip decoding when using Using the suggested wrapper for read seems to fix this issue:
|
The current version of sphinx has problems fetching the intersphinx inventory files: sphinx-doc/sphinx#3234
Fixed at cea72dd. |
I'm still seeing this problem with 1.5.3 and python 3.5.3:
And the error message is not really helpful.. |
When I add a print on line 127 it shows something with zlib and also the bare value error: if 'zlib' not in line:
print('zlib')
raise ValueError
Commenting out the check completely gives a new error:
Any idea @tk0miya? |
Hmm, more investigation is needed. In addition, could you file a new issue? |
sphinx-doc/sphinx#3234 should be fixed now.
sphinx-doc/sphinx#3234 should be fixed now.
sphinx-doc/sphinx#3234 should be fixed now.
sphinx-doc/sphinx#3234 should be fixed now.
With the latest developer version of Sphinx (and 1.5) I see the following warnings/errors:
This works fine with 1.4.8. Unfortunately many of these intersphinx objects.inv files are beyond my control, so I cannot simply re-generate them all with Sphinx 1.5. This seems like a pretty big backward-incompatibility. Would it be possible to restore backward-compatibility in 1.5.1?
The text was updated successfully, but these errors were encountered: