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 steve.dower
Recipients christian.heimes, steve.dower, vstinner
Date 2019-07-05.15:24:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1562340274.55.0.152253745901.issue37505@roundup.psfhosted.org>
In-reply-to
Content
Yeah, at some point we had to add an initialization check to the audit calls because of the tuple, so it essentially became a subinterpreter event but not the main one.

But I thought the dtrace call happened before that check? Looking through the linked commit, apparently not, but I don't actually recall right now why and I can't quite see enough context. Did we need the tuple there too?
History
Date User Action Args
2019-07-05 15:24:34steve.dowersetrecipients: + steve.dower, vstinner, christian.heimes
2019-07-05 15:24:34steve.dowersetmessageid: <1562340274.55.0.152253745901.issue37505@roundup.psfhosted.org>
2019-07-05 15:24:34steve.dowerlinkissue37505 messages
2019-07-05 15:24:34steve.dowercreate