-
-
Notifications
You must be signed in to change notification settings - Fork 31.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
3.4.1rc1 test_pydoc fails: pydoc_data.topics.topics values are type "bytes" not "str" #65630
Comments
Something went wrong with the update of pydoc_data topics for 3.4.1rc1. As can be seen in http://hg.python.org/releasing/3.4.1/rev/c67a19e11a71, the values for the topics dict should be strings but were updated as bytes. This causes pydoc topics searches to fail. The process problem needs to be fixed for 3.4.1 final. An example: $ /usr/local/bin/pydoc3.4 def
Traceback (most recent call last):
File "/usr/local/bin/pydoc3.4", line 5, in <module>
pydoc.cli()
File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/pydoc.py", line 2580, in cli
help.help(arg)
File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/pydoc.py", line 1860, in help
elif request in self.keywords: self.showtopic(request)
File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/pydoc.py", line 1941, in showtopic
pager(doc.strip() + '\n')
TypeError: can't concat bytes to str |
3.4.1rc1 is the first release I've cut where the makefile didn't auto-download Sphinx. And then the makefile used "python" and "sphinx-build" straight off the path, rather than finding the local ones. To generate pydoc-topics, I had to do the following: % ./configure --prefix= And apparently this didn't work. Maybe there should be a "smoke test" to make sure pydoc-topics is okay? And... maybe "make pydoc-topics" should copy the data file itself, rather than making me cut and paste paths out of PEP-101? And *then* automatically test it? |
From a first quick look, it appears that the problem occurs when using a Python 3 version of sphinx-build. With Python 2, the topics appear to be generated correctly. |
The problem is in PydocTopicsBuilder in Doc/tools/sphinxext/pyspecific.py. It needs to be smarter so that ideally it should continue to work with any Python >= 2.5 and independent of the Python being built. |
Well, surely working with the current python is sufficient? I'd be happy if it was only guaranteed to run with the python tree it's a part of. |
New changeset d71c351a6a0f by Georg Brandl in branch '3.4': |
Should be fixed now. I didn't merge into default since someone (cough) has to null-merge all the release related stuff first. |
New changeset 1248796b7945 by Ned Deily in branch 'default': |
To expedite matters, I did the almost-null post-release cleanup merge and then merged the fix for this issue. So I think this issue is now complete. |
If this is fixed, then how come I hit it again today? |
It was just fixed today, after the release. |
Oh, because it was only fixed today. As Emily Litella used to say... never mind! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: