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 izbyshev
Recipients eryksun, izbyshev, steve.dower, vstinner
Date 2020-12-06.08:15:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> So it should be, "if they fail and you're in a context where exceptions are allowed, raise an exception" (which will chain back to the one raised from an audit hook".

What exception should be raised if _Py_fopen() fails (returns NULL)? We can't just check errno anymore because _Py_fopen() might have failed because of the audit hook and thus didn't set errno. So it seems to me that addition of audit hooks broke the implicit contract of _Py_fopen()/_Py_wfopen(), and callers were not fixed.
Date User Action Args
2020-12-06 08:15:29izbyshevsetrecipients: + izbyshev, vstinner, eryksun, steve.dower
2020-12-06 08:15:29izbyshevsetmessageid: <>
2020-12-06 08:15:29izbyshevlinkissue42569 messages
2020-12-06 08:15:28izbyshevcreate