Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | fix virtualenv activation | Maximilian Hils | 2015-08-19 | 1 | -1/+1 |
| | |||||
* | dev script: fix Linux+vagrant+virtualenv | Maximilian Hils | 2015-08-07 | 1 | -1/+1 |
| | |||||
* | merged with upstream changes in dev | Jim Shaver | 2015-06-23 | 1 | -2/+3 |
| | |||||
* | Add a check to see if virtualenv is installed. | Jim Shaver | 2015-06-23 | 1 | -2/+2 |
| | |||||
* | ./dev: echo what we have done | Maximilian Hils | 2015-03-14 | 1 | -1/+6 |
| | |||||
* | simplify virtualenv | Maximilian Hils | 2015-03-14 | 1 | -11/+1 |
| | | | | | | | | - add dev.bat for Windows users - remove ~/.pipcache creation. If that causes issues with PyInstaller, we should use pip --no-cache-dir there or rm -r pip.locations.USER_CACHE_DIR. - remove superfluous pip install calls. | ||||
* | Virtualenv is the one and only recommended dev environment | Aldo Cortesi | 2015-03-12 | 1 | -0/+16 |
- Create a "dev" script to create a virtualenv-based dev environment - Update the docs to remove non-virtualenv install recommendations - Update osx-binaries generation to use virtualenv TODO: - The dev script or an equivalent should be made to work on Windows - We still can't remove the annoying top-level command scripts, because pyinstaller doesn't support entry points. Once it does, they can go. |