summaryrefslogtreecommitdiff
path: root/setup.py
Commit message (Collapse)AuthorAgeFilesLines
* Pass python_requires argument to setuptools (#154)Jon Dufresne2018-10-301-0/+1
| | | | | | | | | | | | | | | | | | Helps pip decide what version of the library to install. https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires > If your project only runs on certain Python versions, setting the > python_requires argument to the appropriate PEP 440 version specifier > string will prevent pip from installing the project on other Python > versions. https://setuptools.readthedocs.io/en/latest/setuptools.html#new-and-changed-setup-keywords > python_requires > > A string corresponding to a version specifier (as defined in PEP 440) > for the Python version, used to specify the Requires-Python defined in > PEP 345.
* Added py37 (#149)Alex Gaynor2018-07-041-0/+1
| | | | | | | | | | | | * Added py37 to jenkins * Added py37 to tox * Added py37 trove classifier * Added py37 to travis * Added py37 to wheel builder
* Add useful trove classifiers (dev status & license) (#143)Jon Dufresne2018-06-161-0/+2
| | | | | | The trove classifiers are displayed on PyPI and so helps inform library users about the project. Document that the project is stable and ready for use in production. Document the project is licensed under the Apache software license.
* blacklist pytest 3.3.0 because it's broken (#135)Alex Gaynor2017-12-041-2/+2
| | | | | | * blacklist pytest 3.3.0 because it's broken * here too
* Drop Python 2.6 and 3.3 support (#133)Hugo2017-10-191-2/+0
| | | | | | | | | | | | | | * Don't test on EOL Python 2.6 * Remove unnecessary positional formatters for Python 2.7+ * Remove branch restriction to test feature branches * Leave PyPy compatibility at 2.6+ * Don't test on EOL Python 3.3 * Don't test feature branches
* bump pytest version (#120)Alex Gaynor2017-08-101-2/+2
|
* Blacklist pytest version which breaks things (#118)Alex Gaynor2017-08-061-2/+2
| | | | | | | | * Use setup.py to get dep info * Blacklist pytest version which breaks things * oops
* We do the py36 (#102)Alex Gaynor2017-01-011-0/+2
|
* Utf8 fix (#100)Paul Kehrer2016-12-171-1/+2
| | | | | | * build with Python2 in non-utf8 environments * pep8 fix
* raise a decent error if pypy <2.6 + update READMEPaul Kehrer2016-02-131-0/+9
|
* drop python 3.2Alex Gaynor2015-10-171-1/+1
|
* Migrate to using CFFI 1.0Donald Stufft2015-06-111-42/+13
| | | | | | | * Move everything under src/ to ensure we test against the installed library. * Create a build_bcrypt.py script which will build _bcrypt.so. * Refactor to utilize the new _bcrypt.so instead of implicit compile.
* Removed usage of mock which wasn't really doing anythingAlex Gaynor2014-12-061-2/+0
|
* scrapped attribute dict in setup.py, it wasn't doing muchAlex Gaynor2014-12-051-21/+8
|
* Upgrade crypt_blowfish to 1.3Donald Stufft2014-12-051-1/+1
|
* Port the setup.py from pyca/cryptography to bcryptDonald Stufft2014-12-051-25/+185
|
* Enable flake8 style checksDonald Stufft2014-12-051-4/+4
|
* Switch to using sixDonald Stufft2014-12-051-0/+5
|
* Use a more consistent name for the compiled moduleDonald Stufft2013-05-111-1/+9
| | | | | | | | CFFI generates a modulename based on the values passed to verify, however this doesn't work very well when those values might change because of installation version runtime. This forces a more consistent name based on values we control instead of values that CFFI deems useful.
* Add tests to ensure behaviorDonald Stufft2013-05-101-2/+8
|
* Package the bcrypt libraryDonald Stufft2013-05-101-0/+92