NotificationsYou must be signed in to change notification settings
Fork33.3k
Star69.7k

[3.11] gh-107913: Fix possible losses of OSError error codes (GH-107930)#108524

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

serhiy-storchaka merged 2 commits intopython:3.11fromserhiy-storchaka:backport-2b15536-3.11

Aug 27, 2023

Merged

[3.11] gh-107913: Fix possible losses of OSError error codes (GH-107930)#108524

serhiy-storchaka merged 2 commits intopython:3.11fromserhiy-storchaka:backport-2b15536-3.11

Aug 27, 2023

Conversation

Copy link

Member

serhiy-storchaka commentedAug 26, 2023•
edited by bedevere-bot
Loading

Functions like PyErr_SetFromErrno() and SetFromWindowsErr() should be called immediately after using the C API which sets errno or the Windows error code.
(cherry picked from commit2b15536)

Issue:PyErr_SetFromErrno() etc should be called immediately after setting the error code #107913

[3.11]pythongh-107913: Fix possible losses of OSError error codes (p…

7a812f6

…ythonGH-107930)Functions like PyErr_SetFromErrno() and SetFromWindowsErr() should becalled immediately after using the C API which sets errno or the Windowserror code..(cherry picked from commit2b15536)Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>

This was referencedAug 26, 2023

PyErr_SetFromErrno() etc should be called immediately after setting the error code#107913

Closed

gh-107913: Fix possible losses of OSError error codes#107930

Merged