- Sep 08, 2017
-
-
Ed Morley authored
* Add a test for the cryptography (cffi) compile step Since it's currently untested. * Skip vendoring libffi/libmemcached on Heroku-16 Unlike for Cedar-14, Heroku-16 comes with these packages pre-installed: https://github.com/heroku/stack-images/blob/5a341970cfc1f201014262ad64c3b3e47514f663/heroku-16/installed-packages.txt#L111 https://github.com/heroku/stack-images/blob/5a341970cfc1f201014262ad64c3b3e47514f663/heroku-16/installed-packages.txt#L172 As such the build scripts had already been made a no-op on Heroku-16: https://github.com/heroku/heroku-buildpack-python/blob/fedae5ceda5a42f594012f911c3808dd5dc6fd9e/builds/libraries/vendor/libffi#L6-L9 https://github.com/heroku/heroku-buildpack-python/blob/fedae5ceda5a42f594012f911c3808dd5dc6fd9e/builds/libraries/vendor/libmemcache#L6-L9 ...meaning the Heroku-16 archives for them on S3 contain zero files. However until now, the buildpack was still unnecessarily downloading and extracting these empty archives - and not just on the first compile (like on cedar-14), but every compile since the directory check will never succeed.
-
- Aug 03, 2017
-
-
Kenneth Reitz authored
* fixed the bug for pypy-5.8.0 * enable shellcheck in makefile Signed-off-by:
Kenneth Reitz <me@kennethreitz.org> * make compile script shellcheck compatible Signed-off-by:
-
- Jun 02, 2017
-
-
Kenneth Reitz authored
* Revert "use pkg_resources to check for distributions (#395)" This reverts commit 9b185f99. * use sp-grep for django detection * sp-grep * fix setuptools script
-
- May 30, 2017
-
-
David Lord authored
more accurate than parsing requirements.txt fixes #359
-
- Mar 17, 2017
-
-
Kenneth Reitz authored
-
- Mar 14, 2017
-
-
Kenneth Reitz authored
-
- Mar 10, 2017
-
-
Kenneth Reitz authored
-
- Sep 16, 2016
-
-
Andrew Pinkham authored
- Add argon2-cffi - Add django[argon2] option from Django docs: https://docs.djangoproject.com/en/1.10/topics/auth/passwords/#argon2-usage
-
- Aug 02, 2016
-
-
Ed Morley authored
For both the cedar and cedar-14 stacks, the libffi directory is named `libffi-3.1` not `libffi-3.1.1`, so the existing library wouldn't be detected, causing it to be re-downloaded during every compile.
-
Ed Morley authored
Since we need to set it regardless of whether the vendored library existed previously or not.
-
- May 13, 2016
-
-
Alex Gaynor authored
-
- May 10, 2016
-
-
Chad Whitacre authored
-
- Apr 21, 2016
-
-
Ed Morley authored
To reduce confusion for users who have not explicitly listed cffi as a dependency. Fixes #142.
-
- Feb 29, 2016
-
-
Ed Morley authored
To save the 301s.
-
- Feb 23, 2016
-
-
Andrew Pinkham authored
This ensures that libffi, required by bcrypt, is installed when Django is installed with the bcrypt dependency declared as an extra (django[bcrypt] or Django[bcrypt]).
-
- Feb 16, 2016
-
-
Alex Gaynor authored
-
- Jun 05, 2015
-
-
Kenneth Reitz authored
fixes #231
-
- Apr 24, 2015
-
-
Steven F authored
Some people use pyOpenSSL (it is the literal name, e.g.: https://pypi.python.org/pypi/pyOpenSSL)
-
- Mar 18, 2015
-
-
Kenneth Reitz authored
-
- Mar 17, 2015
-
-
Kenneth Reitz authored
-
- Jan 14, 2015
-
-
James Arthur authored
-
- Oct 06, 2014
-
-
Jan Aage Lavik authored
-
- Sep 26, 2014
-
-
Samuel Lucidi authored
-
- Aug 04, 2014
-
-
Kenneth Reitz authored
-
- Aug 02, 2014
-
-
Kenneth Reitz authored
-
Kenneth Reitz authored
-
Kenneth Reitz authored
-
