[issue31305] 'pydoc -w import' report "no Python documentation found for 'import'"

Irit Katriel added the comment: It is still relevant, but there is another issue for this: issue11831. -- nosy: +iritkatriel resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> "pydoc -w" causes "no Python documentation found" error when the path is

[issue31305] 'pydoc -w import' report "no Python documentation found for 'import'"

Change by Serhiy Storchaka : -- components: +Library (Lib) type: behavior -> enhancement versions: +Python 3.10 -Python 2.7, Python 3.5 ___ Python tracker ___

[issue31305] 'pydoc -w import' report "no Python documentation found for 'import'"

Joannah Nanjekye added the comment: Given EOL is this still relevant? as it is marked 2.7 -- nosy: +nanjekyejoannah ___ Python tracker ___

[issue31305] 'pydoc -w import' report "no Python documentation found for 'import'"

New submission from Karthikeyan Singaravelan : > Run "pydoc -w " to write out the HTML documentation for a module to a file named ".html". As mentioned in the help this works only for modules and since import is a keyword it throws an error. Maybe this could be added as an enhancement?

[issue31305] 'pydoc -w import' report "no Python documentation found for 'import'"

Changes by Morris Li : -- versions: +Python 3.5 ___ Python tracker ___ ___

[issue31305] 'pydoc -w import' report "no Python documentation found for 'import'"

Changes by Morris Li : -- assignee: docs@python components: Documentation nosy: docs@python, limuyuan priority: normal severity: normal status: open title: 'pydoc -w import' report "no Python documentation found for 'import'" type: behavior versions: Python 2.7