Nathan West added the comment:
Not quite, no. The issue looks like this:
user@host ~/test> python3 -mvenv env
user@host ~/test> true
user@host ~/test> false
user@host ~/test [1]> source env/bin/activate.fish
(env) user@host ~/test> true
(env) user@host ~/test> false
(env) user@host ~/test> deactivate
user@host ~/test> true
user@host ~/test> false
user@host ~/test [1]>
Notice that, after running the `false` command the first time, the command
prompt includes a "[1]", indicating the exit status of the `false` command.
However, after activating the virtual environment, the command prompt no longer
shows the error code from the `false` command. After deactivating the
virtualenv, the command prompt once again displays the error code from `false`.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25671>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
