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.

Author matrixise
Recipients docs@python, matrixise, tomerv
Date 2019-05-14.08:34:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

Thank you for your feedback.

In fact, there is a limitation with the current search engine of Sphinx (because we use it for the documentation). For example, if you try to find the meaning of "for", for us it's a keyword but for the search engine, it will try to find all the sections containing "for" (formatter, platform, argparse.ArgumentParser.format_help, etc...).

For that, we could open an issue on the repository of Sphinx.

Now, about the decorators.

In the definition of a function, we explain the call of a decorator, See the grammar.

A function definition may be wrapped by one or more decorator expressions. Decorator expressions are evaluated when the function is defined, in the scope that contains the function definition. The result must be a callable, which is invoked with the function object as the only argument. The returned value is bound to the function name instead of the function object. Multiple decorators are applied in a nested fashion. For example, the following code

But because it's a specification of the language which has been described with 2 PEPs you can read it on the PEP Index page.

-> Introduced in 2.4

-> Introduced in 3.0

Now, I suggest one thing, add a link to the PEPs in this section
Date User Action Args
2019-05-14 08:34:32matrixisesetrecipients: + matrixise, docs@python, tomerv
2019-05-14 08:34:32matrixisesetmessageid: <>
2019-05-14 08:34:32matrixiselinkissue36913 messages
2019-05-14 08:34:32matrixisecreate