I'm forwarding bug #689431 from Debian [1]:
"Eike discovered that bpython does not cleanly pass on the script's exit status to the parent shell in interactive mode.
Example:
- Call bpython.
- Type exit(120)
- Check with echo $?
Result:
$ bpython; echo $?
# enter exit(120)
0
Expected result:
$ bpython; echo $?
# enter exit(120)
120"
And indeed, the vanilla Python interpreter exits with 120 in that case.
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689431
I'm forwarding bug #689431 from Debian [1]:
"Eike discovered that bpython does not cleanly pass on the script's exit status to the parent shell in interactive mode.
Example:
Result:
$ bpython; echo $?
# enter exit(120)
0
Expected result:
$ bpython; echo $?
# enter exit(120)
120"
And indeed, the vanilla Python interpreter exits with 120 in that case.
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689431