-
-
Notifications
You must be signed in to change notification settings - Fork 36.6k
Exit code in case of an error is always 1 since Python 3.13 #129900
Copy link
Copy link
Closed
Labels
3.13bugs and security fixesbugs and security fixes3.14bugs and security fixesbugs and security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)topic-replRelated to the interactive shellRelated to the interactive shelltype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Description
Activity
Metadata
Metadata
Assignees
Labels
3.13bugs and security fixesbugs and security fixes3.14bugs and security fixesbugs and security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)topic-replRelated to the interactive shellRelated to the interactive shelltype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Bug report
Bug description:
We noticed a failure of our Vim test suite on the Github Windows runners, when it was updated from python3.12 to python3.13.
Vim basically does run in a terminal
exit(123)and expects the return code to be 123, however, since python3.13 the return code seems to be 1.Note this works find on the linux jobs, just on Windows this does not work correctly. Also note, python3 -c 'exit(123)' seems to work correctly, only when using an interactive session it doesn't seem to work right.
related:
CPython versions tested on:
3.13
Operating systems tested on:
Windows
Linked PRs
SystemExitreturn codes when the REPL is started from the command line #129901SystemExitreturn codes when the REPL is started from the command line (GH-129901) #131734