The "scripts" directory was removed since commands are generated at
install-time. So local_run must "install" weboob to run the commands,
albeit it will do it in a very local virtualenv folder.

Laurent Bachelier authored Jul 13, 2018 and hydrargyrum committed Aug 13, 2018

Especially with local_run

Laurent Bachelier authored Aug 07, 2018 and hydrargyrum committed Aug 10, 2018

That way you can do "local_run -Wall boobank"
-Wall was previously not working at all, being passed as argv[0], and
gets quickly annoying.

Laurent Bachelier authored Aug 06, 2018 and hydrargyrum committed Aug 10, 2018

Without it, sys.executable became '' and would end up confusing
some virtualenv installs.

Phyks (Lucas Verney) authored Oct 12, 2016 and Laurent Bachelier committed Oct 25, 2016

When `$PYTHONPATH` was not set, the `local_run.py` was setting a
`$PYTHON_PATH` which was only containing the script directory. It was
blocking when trying to run another Python script which was making use
of Weboob API, as well as loading other non Python stdlib modules.

Signed-off-by: Phyks (Lucas Verney) <phyks@phyks.me>

related to e93d724e

When installing weboob in $HOME, the weboob base modules (weboob.browser...)
are installed in $HOME/.local/lib/python2.7/site-packages/... (see PEP-370).
When running weboob from the source directory with tools/local_run.sh, those
base modules are read from $HOME/.local instead of the source directory.
Passing the "-s" option to python makes it ignore $HOME/.local and read the
base modules from the source directory.

Signed-off-by: Matthieu Weber <mweber+weboob@free.fr>

python modernize.py --no-six -f libmodernize.fixes.fix_print -w

With manual fixes as the import was put always on top.

Laurent Bachelier authored May 09, 2013 and Romain Bignon committed May 14, 2013

This allows running any weboob script, not only those in scripts/