From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: seb@k-7.ch, Stefan Kangas <stefan@marxist.se>,
Noam Postavsky <npostavs@gmail.com>,
31405@debbugs.gnu.org
Subject: bug#31405: 25.3; Python.el doesn't provide infos to info-lookup-symbol
Date: Thu, 12 Aug 2021 16:13:34 +0100 [thread overview]
Message-ID: <871r6yd7c1.fsf@tcd.ie> (raw)
In-Reply-To: <87k0kqkayt.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 12 Aug 2021 16:13:14 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Stefan Kangas <stefan@marxist.se> writes:
>
>> 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.)
>
> The Melpa package doesn't seem to exist any more? So I'm guessing there
> isn't much demand for an Info manual for Python, so adding support for
> it in info-look would just be frustrating the users, I think.
>
> On the other hand, you have a point that if Emacs did provide hooks into
> Info, then perhaps it'd entice people to start distributing .info
> files...
FWIW, Debian packages the latest Python Info manual as python3-doc.
> Hm...
>
> Oh! I was looking in melpa-stable -- python-info is indeed in melpa.
Yes, but at first glance it seems to be specific to Python 2 and hasn't
been updated in 6 years.
> OK, I've now added support for python-mode in info-lookup-symbol, and
> seems to work in my one test, which was looking up "date", which took me
> to:
>
> -- Class: datetime.date (year, month, day)
>
> All arguments are required. Arguments may be ints or longs, in the
> following ranges:
>
> Which seems correct. People who actually use Python should probably
> change
>
> (info-lookup-maybe-add-help
> :mode 'python-mode
> :doc-spec '(("(python)Index")))
>
> to something that filters/matches more accurately, perhaps.
In my case I have to override it as
(with-eval-after-load 'info-look
(info-lookup-add-help
:mode 'python-mode
:doc-spec '(("(python3.9)Index"))))
to match the name and version of the manual installed by Debian.
Thanks,
--
Basil
next prev parent reply other threads:[~2021-08-12 15:13 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
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 [this message]
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=871r6yd7c1.fsf@tcd.ie \
--to=bug-gnu-emacs@gnu.org \
--cc=31405@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.com \
--cc=seb@k-7.ch \
--cc=stefan@marxist.se \
/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).