- Dec 15, 2019
-
-
hydrargyrum authored
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.
-
- Oct 27, 2019
-
-
- Sep 10, 2019
-
-
- Aug 13, 2018
-
-
Especially with local_run
-
- Aug 09, 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.
-
Without it, sys.executable became '' and would end up confusing some virtualenv installs.
-
- 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>
-
- Jul 17, 2015
-
-
Laurent Bachelier authored
related to e93d724e
-
- Feb 27, 2015
-
-
Matthieu Weber authored
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>
-
- Oct 06, 2014
-
-
Laurent Bachelier authored
python modernize.py --no-six -f libmodernize.fixes.fix_print -w With manual fixes as the import was put always on top.
-
- Sep 05, 2014
-
-
- May 26, 2014
-
-
Laurent Bachelier authored
-
- Dec 30, 2013
-
-
Laurent Bachelier authored
-
- Jul 19, 2013
-
-
- May 14, 2013
-
-
This allows running any weboob script, not only those in scripts/
-
- Apr 09, 2013
-
-
- Apr 05, 2013
-
-
Laurent Bachelier authored
-
- Mar 25, 2013
-
-
Laurent Bachelier authored
-
Laurent Bachelier authored
-