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 r.david.murray
Recipients JelleZijlstra, nedbat, r.david.murray, yselivanov
Date 2016-06-02.19:02:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464894127.82.0.0995415240128.issue19611@psf.upfronthosting.co.za>
In-reply-to
Content
The patch looks reasonable to me.  I've added Yuri to nosy since he's responsible for the signature code in inspect, and he might have an opinion on the appriateness of the fix.

I think this special case needs to be documented, since currently the name is documented as needing to be a valid python identifier.

Sounds like we don't have a good answer to Ned's question about a 2.7 workaround.  On the other hand, "fragile byte code inspection" is not really fragile, since the 2.7 bytecode will never change.  The real question is if someone cares enough to do the work, since as you say (and Ned admits) the benefit is small.
History
Date User Action Args
2016-06-02 19:02:07r.david.murraysetrecipients: + r.david.murray, nedbat, yselivanov, JelleZijlstra
2016-06-02 19:02:07r.david.murraysetmessageid: <1464894127.82.0.0995415240128.issue19611@psf.upfronthosting.co.za>
2016-06-02 19:02:07r.david.murraylinkissue19611 messages
2016-06-02 19:02:07r.david.murraycreate