| Age | Commit message (Collapse) | Author |
|---|
|
this commit deliberately *duplicates* the dependency information between
the setup.py and requirements.pip.
The rationale behind it is that one of them is the generic dependency
information, to be passed to system helpers in order to package it.
The requirements.pip has any pinning information that we want to impose
during development, and it behaves as a well-known set.
Read https://caremad.io/posts/2013/07/setup-vs-requirement/ for more
explanations.
- Resolves: #8830
|
|
this is part of a process to make the setup of the development mode less
troublesome. from now on, setting up a virtualenv in pure development
mode will be as easy as telling pip to just install the external dependencies::
pip install -r pkg/requirements.pip
and traversing all the leap repos for the needed leap dependencies doing::
python setup.py develop
- Related: #7288
|
|
* add versioneer (patched for our particular repo config)
* add parse_requirements to unify requirement handling
|
