[3.13] gh-141930: Use the regular IO stack to write .pyc files for a better error message on failure (GH-141931)#142023
Merged
Yhg1s merged 1 commit intopython:3.13from Dec 1, 2025
Conversation
…for a better 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 commit 656a64b) Co-authored-by: Stefano Rivera <stefano@rivera.za.net>
cmaloney
requested review from
brettcannon,
ericsnowcurrently,
ncoghlan and
warsaw
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
.pycif unable to completely write a.pycfile in one go #141930