[Cloud] Re: Source command not working with zsh

Well, chsh would not work here because when you run it, it'll ask for a password and tool accounts (the ones you use "become" command to log in as) are not passworded accounts. On Thu, Nov 11, 2021 at 7:52 PM Roy Smith wrote: > The standard way to change your login shell is with "chsh". In theo

[Cloud] Re: Source command not working with zsh

The standard way to change your login shell is with "chsh". In theory you should be able to do: $ chsh -s /usr/bin/zsh and the next time you login, that should be your shell. "man chsh" for more details. I say "in theory" because I've never tried it on toolforge. I can't see any reason why

[Cloud] Re: Source command not working with zsh

I like that idea! Will try it. In the meantime, I am still eager to know why *source* is failing (only with zsh and only if called from within a .sh script). And also about the proper way to change the shell for tools accounts. On Thu, Nov 11, 2021 at 7:04 PM AntiCompositeNumber < anticompositenu

[Cloud] Re: Source command not working with zsh

Instead of activating the virtual environment, you can call the python executable directly by its path, ie `venv/bin/python yourscript.py`. This will work largely the same as activating the venv, except that you have to always make sure to call the right executable, the shell won't figure it out fo

[Cloud] Source command not working with zsh

Hi all, Starting Nov 7, a number of the jobs I would run through Toolforge grid have stopped working. Each job consists of a .sh file like this on the first line of which I use the source command to activate a p