From: Stefan Kangas <stefan@marxist.se>
To: Noam Postavsky <npostavs@gmail.com>
Cc: seb@k-7.ch, 31405@debbugs.gnu.org
Subject: bug#31405: 25.3; Python.el doesn't provide infos to info-lookup-symbol
Date: Fri, 23 Aug 2019 09:04:21 +0200 [thread overview]
Message-ID: <CADwFkmkpvG0L5byV1UdBh_phqSUpNJ1cUifmh7oVsLnBQ0qSgg@mail.gmail.com> (raw)
In-Reply-To: <8736yz4jp9.fsf@k-7.ch>
npostavs@gmail.com writes:
> tags 31405 + moreinfo
> quit
>
> seb@k-7.ch (Sébastien Gendre) writes:
>
>> In a buffer with python-mode, after run Emacs function
>> 'info-lookup-symbol', Emacs ask which mode would provide him infos about
>> Python symbols. I can choose between c-mode, awk-mode, etc, but there's
>> no python-mode provided. :(
>>
>> It would be nice if python-mode provide infos about Python symbols.
>> Informations about Python symbols can be found with the executable
>> 'pydoc' provided with the Python interpreter.
>
> Does 'pydoc' provide output formatted as .info though? Not sure if this
> feature request makes sense.
Sphinx is used to generate Python docs AFAIK, and it supports info
format output. There is also the MELPA package python-info which is
"a simple Emacs package to provide an info manual for Python":
https://github.com/wilfred/python-info
Perhaps we should support that use case in vanilla Emacs? One can
always hope that more GNU/Linux distributions takes the hint and
starts generating and shipping the info files for Python. (And that
interested users files bugs with their respective GNU/Linux
distribution, Homebrew for OSX, etc. if they don't already do that.)
Thanks,
Stefan Kangas
next prev parent reply other threads:[~2019-08-23 7:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 15:24 bug#31405: 25.3; Python.el doesn't provide infos to info-lookup-symbol Sébastien Gendre
2019-05-07 17:36 ` npostavs
2019-08-23 7:04 ` Stefan Kangas [this message]
2021-08-12 14:13 ` Lars Ingebrigtsen
2021-08-12 15:13 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-12 15:21 ` Lars Ingebrigtsen
2021-08-12 15:42 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-28 9:56 ` Augusto Stoffel
2021-08-28 10:05 ` Eli Zaretskii
2021-08-12 16:06 ` Eli Zaretskii
2021-08-12 16:02 ` Eli Zaretskii
2021-08-13 11:34 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmkpvG0L5byV1UdBh_phqSUpNJ1cUifmh7oVsLnBQ0qSgg@mail.gmail.com \
--to=stefan@marxist.se \
--cc=31405@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--cc=seb@k-7.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).