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 scoder
Recipients benjamin.peterson, eric.araujo, larry, ncoghlan, pitrou, python-dev, scoder, terry.reedy, yselivanov
Date 2014-02-03.07:06:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> Also, PEP 8 forbids using annotations in the CPython library, which
> includes all of CPython's builtins.  So using annotations in any way
> for this was off the table.

Interesting, wasn't aware of that. Then let's wait what will happen when
users start manually adding signature information to the docstrings of
their C code extensions and come asking for annotation support in order to
allow for introspection of the expected parameter types.

> You imply that __text_signature__ is improper and unsafe.

What I'm saying is that the existing function introspection API would have
provided a much better way to do these things, and that it's good to
finally have the meta data available in the source code so that that API
can be made available at some point. Sorry if my wording sounded offensive.

> If in the future we need to change how we represent signatures, we can
> remove it.  It's an undocumented internal implementation detail and we
> have free license to do so.

I don't think that's possible any more once it's out in the wild. The
feature is just way too visible.
Date User Action Args
2014-02-03 07:06:26scodersetrecipients: + scoder, terry.reedy, ncoghlan, pitrou, larry, benjamin.peterson, eric.araujo, python-dev, yselivanov
2014-02-03 07:06:26scoderlinkissue17159 messages
2014-02-03 07:06:26scodercreate