From: kobarity <kobarity@gmail.com>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
63622@debbugs.gnu.org
Subject: bug#63622: lisp/progmodes/python.el: performance regression introduced by multiline font-lock
Date: Wed, 24 May 2023 08:21:11 +0900 [thread overview]
Message-ID: <eke7lehehbx4.wl-kobarity@gmail.com> (raw)
In-Reply-To: <CA+G3_PPfM+0ASFXtTJmdZnkQrqXcW0qFLVDeoGFt9e2rmFDbpg@mail.gmail.com>
Hi Stefan and Tom,
Thank you very much for your confirmation.
Tom Gillespie wrote:
> While we're here I think [fF]? should probably be included in the prefix since
> format strings are also valid docstrings.
Is that so? As far as I have tried, f-string does not seem to be a
docstring.
Python 3.11.3 (main, May 2 2023, 21:12:31) [GCC 11.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> def f1():
... "docstring"
...
>>> f1.__doc__
'docstring'
>>> def f2():
... f"not docstring"
...
>>> f2.__doc__
>>> a = 1
>>> def f3():
... f"not docstring {a}"
...
>>> f3.__doc__
>>>
next prev parent reply other threads:[~2023-05-23 23:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 3:14 bug#63622: lisp/progmodes/python.el: performance regression introduced by multiline font-lock Tom Gillespie
2023-05-21 4:53 ` bug#63622: source of problem identified to be python-font-lock-extend-region Tom Gillespie
2023-05-21 6:08 ` bug#63622: lisp/progmodes/python.el: performance regression introduced by multiline font-lock Eli Zaretskii
2023-05-21 7:13 ` Tom Gillespie
2023-05-21 9:31 ` kobarity
2023-05-21 15:16 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-22 14:58 ` kobarity
2023-05-22 15:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-23 15:45 ` kobarity
2023-05-23 17:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-23 19:04 ` Tom Gillespie
2023-05-23 23:21 ` kobarity [this message]
2023-05-24 18:53 ` Tom Gillespie
2023-05-23 23:41 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-24 15:05 ` kobarity
2023-05-26 10:01 ` Eli Zaretskii
2023-05-21 15:44 ` kobarity
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=eke7lehehbx4.wl-kobarity@gmail.com \
--to=kobarity@gmail.com \
--cc=63622@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tgbugs@gmail.com \
/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).