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
pydoc enum.{,Int}Enum fails #67197
Comments
Not a big deal, but "$ pydoc enum.Enum" and "$ pydoc enum.IntEnum" fail to retrieve the docstrings, while they are visible with "$ pydoc enum". |
This is because bool(enum.Enum) is False. Other example: $ pydoc3 builtins.False
no Python documentation found for 'builtins.False'
$ pydoc3 builtins.True
Help on bool in builtins object: builtins.True = class bool(int)
... Here is simple fix. |
Lgtm, needs a test case. |
The fix is definitely an improvement. Though there is still one obvious flaw remaining, which applies to any attribute that is set to None: $ ~/proj/python/cpython/python -bWall -m pydoc builtins.None
No Python documentation found for 'builtins.None'.
Use help() to get the interactive help utility.
Use help(str) for help on the str class. |
In 3.5 at least 'pydoc None' works. |
I think we can ignore this flaw. 'pydoc None' works, and any solution for None aliases could break existing code that use private pydoc functions. Here is a patch with a test. |
Patch looks good, get it in! :) |
New changeset d1b9eb9de8af by Serhiy Storchaka in branch '2.7': New changeset a480f470c469 by Serhiy Storchaka in branch '3.4': New changeset 03330e5edb37 by Serhiy Storchaka in branch 'default': |
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: