Activate virtualenv environment on terminal launch #19712
|
When I launch a new terminal while an environment is selected, the expected behavior is for the shell to source the activation script of the target env. What happens in my case is that the source command is shown in the terminal but has no effect. When I run the exact same command once the terminal is initialized then it works. source /home/tyassine/.virtualenvs/dev/bin/activate
tyassine@LAP-331:~/Code/ChannelCharting$ source /home/tyassine/.virtualenvs/dev/bin/activate
(dev) tyassine@LAP-331:~/Code/ChannelCharting$ First line appears right after I launch a new terminal. Subsequent lines I ran manually to show the problem. |
Replies: 2 comments 4 replies
|
How complicated is your shell activation? It looks like the terminal is ready before your shell is, and so it's sending the command before the shell is ready to accept input. |
|
My shell activation is pretty basic. The only extra things I do are initializing virtualenvwrapper and setting the |
|
It's possible the virtualenvwrapper activation is what's delaying your shell from being ready when we send the text if that requires a full Python execution which isn't cheap. I'm not sure what to suggest here other than to know we are looking into redoing our terminal story partially because of this sort of issue (which comes up a lot for conda users). You can turn off the automatic activation if you are finding it annoying. |
|
I think you got it right. I disabled the virtualenvwrapper activation and the problem was gone. I tried adding a sleep command in the .bashrc to further investigate and it appears anything longer than 100ms triggers the problem. Thanks for the clarification and I hope the future version addresses these kind of issues. |
|
The setting is |
|
Perfect, thanks! |
My shell activation is pretty basic. The only extra things I do are initializing virtualenvwrapper and setting the
$DISPLAYvariable for VcXsrv. I should mention I use WSL.