NotificationsYou must be signed in to change notification settings
Fork33.5k
Star70.1k

[3.14] gh-141930: Use the regular IO stack to write .pyc files for a better error message on failure (GH-141931)#142021

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

Open

miss-islington wants to merge1 commit intopython:3.14

base:3.14

Choose a base branch

frommiss-islington:backport-656a64b-3.14

Open

[3.14] gh-141930: Use the regular IO stack to write .pyc files for a better error message on failure (GH-141931)#142021

miss-islington wants to merge1 commit intopython:3.14frommiss-islington:backport-656a64b-3.14

Conversation

Copy link

Contributor

miss-islington commentedNov 27, 2025•
edited by bedevere-appbot
Loading

Use open() to write the bytecode
Convert to unittest style asserts
Tweak news, thanks@vstinner
Tidy
reword NEWS, avoid word "retried"
(cherry picked from commit656a64b)

Co-authored-by: Stefano Riverastefano@rivera.za.net

Issue:Python stops trying to create a.pyc if unable to completely write a.pyc file in one go #141930

pythongh-141930: Use the regular IO stack to write .pyc files for a b…

ec6b8c9

…etter error message on failure (pythonGH-141931)* Use open() to write the bytecode* Convert to unittest style asserts* Tweak news, thanks@vstinner* Tidy* reword NEWS, avoid word "retried"(cherry picked from commit656a64b)Co-authored-by: Stefano Rivera <stefano@rivera.za.net>