add doc about activating a python env to bypass the set -e of the environment.sh script

[utke1]

https://github.com/bradbell/cmpad/blob/5b75a10efca647f7b827f5a214580d0c06005bd2/xrst/get_started.xrst#L75C1-L75C26

In the snippet above, the environtment.sh bootstraps the environment fine but shell opened after activation is exited after any command error because this script has set -e cf

cmpad/bin/environment.sh

Line 2 in 5b75a10

set -e -u

So I get kicked out of the environment on any command line error I may make. I propose to add to the documentation that the already created environment should be activated e.g. with

source  build/release/bin/activate 

(or suitably adjusted for "build_type" ) which doesn't have the set -e and I won't get kicked out of the environment upon the first error.

[bradbell]

By default, I always put an set -e -u at the beginning of my bash scripts. Perhaps when one is sourcing a file, instead of opening a new shell, this is not a good idea and we should remove it ? In other words, let the shell that is sourcing the file determine if it wants to have -e and -u set ?

Do you think this would solve your problem ?

[bradbell]

See the commit
e7ea791

Please close this issue if that fixes it for you.