Why would I need to reboot the shell when working on code in any of the projects? Well, if I edit any of the shell scripts (shell.py) the changes won’t be picked up by my shell unless I reboot it somehow.
My first inclination was to find a command for OpenStack along the lines of
source ~/.bashrc but there was no command I could find.
It wasn’t until I pulled from a git repo that had moved to testtools that I recognized that
sudo python setup.py install, executed within the root directory of the project, rebooted the shell to update the version of shell.py that it was sourcing.
I don’t know if this is the only way to reboot the shell when working on changes to shell.py, but so far it seems to be an effective way.
Since I got caught this week moving back to the master branch with a clean git status but with stale responses to shell help, I now incorporate
sudo python setup.py install as part of my workflow. I already executed
git status and
./run_tests.sh everywhere I went and I just throw in
sudo python setup.py install if ever I have less than full confidence that the shell responses are reflective of the shell.py code in the repo in which I am located.
Thanks for supporting this GNOME OPW intern,