summaryrefslogtreecommitdiff
path: root/testing/requirements-testing.pip
AgeCommit message (Collapse)Author
2017-07-08[feat] use OpenSSL backend for scrypt if availableKali Kaneko
This needs OpenSSL >= 1.1, otherwise it will keep using the scrypt dependency. We should think about deprecating scrypt as a dependency when we can be sure that the adoption of libssl 1.1 is wide enough. I think that at some point (soledad 0.11 or so) we can drop the scrypt dependency, which was being somehow problematic at times (the _scrypt.so was not appearing when installing with pip, needed workarounds). From that moment on, we can raise an error if an old libssl is found and no scrypt can be imported - leaving that to the user/packager. In debian stretch and afterwards, you can get that version by installing libssl-dev - Related: #8472
2017-03-17[docs] Define in details the testing environmentefkin
On debian stable the `python3-tox` and `python-tox` packages come with a really old version of `pip` and `setup_tools`. This makes unusable PEP496 that comes handy when dependencies are "py-version-related". As a workaround we can "inject" an upgraded version of `pip` just before running `tox`.