Issue715782
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2003-04-05 11:36 by doko, last changed 2022-04-10 16:08 by admin. This issue is now closed.
Messages (6) | |||
---|---|---|---|
msg15379 - (view) | Author: Matthias Klose (doko) * | Date: 2003-04-05 11:36 | |
[ from http://bugs.debian.org/186775 ] If one uses $ man perl one gets on a path that can lead one to eventually find docs for the most basic commands like 'while' However for python one sees one is to use pydoc. But running pydoc, one just sees pydoc - the Python documentation tool /usr/bin/pydoc <name> ... etc. no hint about how to learn about basics like 'while'. BTW, I wish it would say pydoc, not /usr/bin/pydoc |
|||
msg15380 - (view) | Author: Cherniavsky Beni (cben) * | Date: 2003-04-06 08:33 | |
Logged In: YES user_id=36166 It should suggest to run ``python`` and type ``help()``. Then one can type ``topics`` and access the language documentation itself, e.g. ``LOOPING`` would tell one that there is a ``while`` whose specific documentation is accessible by typing the ``while`` keyword itself. Also some sentences about the usefulness of the Python prompt, `dir()` and `help()` for learning might be in order... BTW, it would be more consistent if pydoc would support the special topics from the command line (it would require a non-ambiguos option to avoid shadowing modules in current directoy that happen to have one of the special name)... |
|||
msg15381 - (view) | Author: Douglas Napoleone (derivin) | Date: 2003-04-19 04:06 | |
Logged In: YES user_id=541557 Could you please include the OS, install, distro for python? the distrobution from ActiveState has a very detailed manpage on linux. The cygwin distrobution (currently hosted/maintained by RedHat) has a poor man page (similar yet different from your example). To be honest, I thought there was only a GNU info page, a quick find of the source tree didnt turn anything up, (but Im building on windows). |
|||
msg15382 - (view) | Author: Tim Peters (tim.peters) * | Date: 2003-04-24 14:29 | |
Logged In: YES user_id=31435 Unassigned (I can't make time for this). |
|||
msg15383 - (view) | Author: Martin v. Löwis (loewis) * | Date: 2003-06-14 09:08 | |
Logged In: YES user_id=21627 This is fixed in pydoc.py 1.85 NEWS 1.783 as far is Python proper is concerned. To get keyword help, the Python HTML documentation must be found in the locations in which it is searched for. The "I wish it would say pydoc" wish will not be granted. Printing the complete path is deliberate, so that users can see where in the path pydoc was found. |
|||
msg15384 - (view) | Author: Matthias Klose (doko) * | Date: 2003-07-05 07:14 | |
Logged In: YES user_id=60903 Is it intended, that 'pydoc while' displays the snippet from the reference manual, while searching in 'pydoc -g' doesn't find anything? |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-10 16:08:02 | admin | set | github: 38266 |
2003-04-05 11:36:50 | doko | create |