Author phr
Recipients docs@python, gvanrossum, phr, rhettinger, veky
Date 2019-10-02.21:42:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1570052555.9.0.591966850606.issue38333@roundup.psfhosted.org>
In-reply-to
Content
Yes, the suggestion was just for the docs, and since those are intended for human rather than machine consumption, it's fine if there are some blurry cases where there is no signature.  Ideally in those cases, the issue should be explained in the doc text.

I actually don't see what's wrong with including signatures in the source code as well, as long as doing so doesn't break anyone's existing code.  I agree with Veky that one should be very hesitant about breaking existing working code, even if that code relies on undocumented behavior.
History
Date User Action Args
2019-10-02 21:42:35phrsetrecipients: + phr, gvanrossum, rhettinger, docs@python, veky
2019-10-02 21:42:35phrsetmessageid: <1570052555.9.0.591966850606.issue38333@roundup.psfhosted.org>
2019-10-02 21:42:35phrlinkissue38333 messages
2019-10-02 21:42:35phrcreate