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
help() does not check for chm file #40888
Comments
Idle looks for the html docs In the source package there are lots of .tex files, Using Windows XP |
Logged In: YES Why do you say IDLE looks for the html docs? On Windows, it |
Logged In: YES Martin, the IDLE help menu has four entries:
Colin, pressing F1 should take you to on-line html docs. If this answers your question. please close the bug. |
Logged In: YES Martin:
Start up an idle(or an interpreter), type help(), and type 'and'. >>> help()
...(snip)
help> and If a PYTHONDOCS environ variable is given to the directory of Otherwise, you get the message: Sorry, topic and keyword documentation is not available You can solve this problem by downloading html docs for |
Logged In: YES I see. This is not a bug in IDLE, though - press F1, or select It is more a problem of the help() function, which does not Notice that Python 2.4 has not been released yet, so there is http://www.python.org/dev/doc/python-docs-devel.tar.bz2 Raymond, what versin of IDLE are you looking at? In the one |
Logged In: YES If anybody wants to tackle this issue: it is possible to hh -decompile c:\python24\doc\html c:\python24 |
Logged In: YES
It's my fault. I didn't know that. Thanks, Martin. |
Logged In: YES Thanks Martin. Also thanks to Raymond for his comments and to George for Colin W. |
Logged In: YES It appears that Raymond customized his IDLE help to add On Windows, EditorWindow.__init__() will try to locate |
Logged In: YES Assuming everybody agrees that the original issue is |
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: