summaryrefslogtreecommitdiff
path: root/requirements
Commit message (Collapse)AuthorAgeFilesLines
* Depend on ruamel 0.16jjardon/ruamelJavier Jardón2019-07-292-16/+2
|
* Introduce Cython to the project and documentBenjamin Schubert2019-05-292-0/+2
| | | | | | | | | | | | | Cython requires a plugin to allow coverage of cython files, which was updated in coveragerc. It also means we need to build the dependencies and install cython for coverage. Cython requires access to both source and compiled files when running coverage. We therefore need to install project in develop mode. Updated documentation to explain how to run tests without tox but with coverage
* requirements: Do not require PyGObjectChandan Singh2019-05-142-4/+0
| | | | | Since !1341 got merged, we do not depend on `PyGObject`. The only thing that needed it was OSTree so this can be safely removed now.
* requirements/Makefile: Do not depend on the "force" packageTristan Van Berkom2019-03-051-2/+2
| | | | Chandan, you silly pony.
* requirements/Makefile: Always rebuild requirements filesChandan Singh2019-03-041-2/+4
| | | | | | | We always want to update all the requirements files together such that the versions of the common dependencies do not drift between them. Do so by adding a dummy phony target `FORCE` and depend on it from all the `.txt` targets.
* tox.ini / requirements: Separated coverage requirementsTristan Van Berkom2019-03-044-14/+25
| | | | Since coverage is optional, lets make it really optional.
* requirements/Makefile: exclude pkg-resourcesChandan Singh2019-02-181-1/+1
| | | | | | | | | Having `pkg-resources` in requirements files is never the right thing as it is not really a package that one can install. This is basically an artifact of Debian-based systems providing incorrect metadata to pip. See [this pip issue](https://github.com/pypa/pip/issues/4022) and [this Ubuntu issue](https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1635463) for more background.
* Cache Keys: Update to use JSON rather than pickledanielsilverstone-ct/json-cache-keyDaniel Silverstone2019-02-142-0/+2
| | | | | | | | This affects the cache key version (updated to 7) and introduces a dependency on `ujson` which is BSD licenced as of the version locked in `requirements.txt` Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
* loadelement.py: Switch from roaringbitmap to pyroaringDaniel Silverstone2019-02-062-6/+2
| | | | | | | | The licence for roaringbitmap was not compatible. pyroaring is a similar project which is MIT licensed and is slightly better on memory too. Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
* requirements: Add roaringbitmap to the requirementsDaniel Silverstone2019-02-052-0/+6
| | | | | | | In order to support use of roaring bitmaps in the loader, we need to depend on it here. Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
* requirements/requirements.in: require Click >= 7.0abderrahim/protobuf-versionAbderrahim Kitouni2019-01-281-1/+1
| | | | This is needed since 629a6e524, and was lost in the conversion to requirements.in
* requirements/requirements.in: require protobuf >= 3.6Abderrahim Kitouni2019-01-281-1/+1
| | | | This is needed since 0f2bc3754
* dev-requirements: pytest-cov==2.6.1 for '--no-cov'Angelos Evripiotis2019-01-111-1/+1
| | | | | | | | | | | | | | | Bump the version of pytest-cov, so that we pick up the fix for the '--no-cov' option breaking in pytest 4.0: https://github.com/pytest-dev/pytest-cov/pull/230 This was the error you would get prior to this version: _pytest.warning_types.RemovedInPytest4Warning: config.warn has been deprecated, use warnings.warn instead Although it says 'deprecated', it did result in termination with stack trace.
* CONTRIBUTING.rst: Add instructions to update requirements fileschandan/update-requirements-one-linerChandan Singh2019-01-041-1/+1
| | | | | | | | Split the "The MANIFEST.in and setup.py" section in two: "Managing data files" and "Updating BuildStream's Python dependencies". Briefly explain the layout of `requirements` directory and add instructions to use the Makefile added in the last commit.
* Add Makefile to update requirements filesChandan Singh2019-01-041-0/+21
|
* Rename "tools" directory to "requirements"Chandan Singh2019-01-046-0/+74
This seems like a better name for the directory, as it more closely describes the purpose of its contents.
View Lorry Controller Status