`sys.exit` unpacks its argument if it is a 0- or 1-element tuple
Open
@picnixz is already working on this.
Since Jun 21, 2025.
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
The documentation of sys.exit says “The optional argument arg can be an integer giving the exit status (defaulting to zero), or another type of object. [...] If another type of object is passed, None is equivalent to passing zero, and any other object is printed to stderr and results in an exit code of 1.” This is no longer true for 0- and 1-element tuples in Python 3.12 and later. It acts like the argument is unpacked: sys.exit(()) is treated like sys.exit() and sys.exit((x,)) is treated like sys.exit(x).
$ python3.11 -c 'import sys; sys.exit(())'; echo $?
()
1
$ python3.12 -c 'import sys; sys.exit(())'; echo $?
0
$ python3.11 -c 'import sys; sys.exit((2,))'; echo $?
(2,)
1
$ python3.12 -c 'import sys; sys.exit((2,))'; echo $?
2
CPython versions tested on:
3.12, 3.13, CPython main branch
Operating systems tested on:
macOS
Linked PRs
- gh-135789
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.