- 06 Mar, 2018 3 commits
-
-
Kenneth Reitz authored
-
Kenneth Reitz authored
Signed-off-by:Kenneth Reitz <me@kennethreitz.org>
-
Kenneth Reitz authored
-
- 02 Mar, 2018 4 commits
-
-
Kenneth Reitz authored
-
Kenneth Reitz authored
* Update pipenv-python-version * use latest versions in pipenv script Signed-off-by:
-
jxltom authored
* Fix PYTHONPATH is not set when running collectstatic * update changelog Signed-off-by: -
Jose Diaz-Gonzalez authored
This is useful if you'd like to customize python binaries without forking the entire buildpack. Similar functionality was implemented in https://github.com/heroku/heroku-buildpack-ruby/pull/238
-
- 17 Feb, 2018 1 commit
-
-
Eugene Pakhomov authored
* Add support for PIP_EXTRA_INDEX_URL * Add support for PIP_EXTRA_INDEX_URL for Pipenv
-
- 16 Feb, 2018 2 commits
-
-
Swen Kooij authored
-
Kenneth Reitz authored
-
- 16 Jan, 2018 1 commit
-
-
Kenneth Reitz authored
* initial stab at pipenv --dev support * test installation output * locale fix * refactor * fix typo * fix typo * ellipsis * polish
-
- 15 Jan, 2018 1 commit
-
-
Kenneth Reitz authored
* changelog notice * v123 * v123
-
- 10 Jan, 2018 1 commit
-
-
Kenneth Reitz authored
-
- 08 Jan, 2018 1 commit
-
-
Kenneth Reitz authored
Update buildpack to latest version of Python.
-
- 02 Jan, 2018 1 commit
-
-
Josh Friend authored
-
- 18 Dec, 2017 1 commit
-
-
Kenneth Reitz authored
* mcount pipenv * more mcount for pip * shellcheck compliance * fix typo Signed-off-by:
-
- 15 Dec, 2017 1 commit
-
-
Robin Richtsfeld authored
-
- 13 Dec, 2017 1 commit
-
-
Kenneth Reitz authored
* make gunicorn default access log to stdout * Update python.gunicorn.sh
-
- 22 Nov, 2017 2 commits
-
-
Kenneth Reitz authored
* fixed the bug for pypy-5.8.0 * changelog Signed-off-by:
-
Josh Friend authored
-
- 15 Nov, 2017 1 commit
-
-
Johannes Hoppe authored
Set GDAL and GEOS library locaiton explicitly in environment variables: * GDAL_LIBRARY_PATH "/app/.heroku/vendor/lib/libgdal.so" * GEOS_LIBRARY_PATH "/app/.heroku/vendor/lib/libgeos_c.so" Django has to settings with the same name. The setup now works as described here: https://devcenter.heroku.com/articles/postgis#geodjango-setup
-
- 14 Nov, 2017 1 commit
-
-
Josh Friend authored
-
- 26 Sep, 2017 2 commits
-
-
Kenneth Reitz authored
* fixed the bug for pypy-5.8.0 * changelog Signed-off-by:
-
🔝 Kenneth Reitz authored* fixed the bug for pypy-5.8.0 * changelog Signed-off-by:
-
- 25 Sep, 2017 1 commit
-
-
Kenneth Reitz authored
* improvements to pipenv Signed-off-by:
-
- 08 Sep, 2017 7 commits
-
-
Johannes Hoppe authored
-
Johannes Hoppe authored
-
Johannes Hoppe authored
-
Kenneth Reitz authored
* only do this on heroku-16 * history Signed-off-by:
-
Kenneth Reitz authored
-
Zach McCormick authored
-
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.
-
- 06 Sep, 2017 1 commit
-
-
Ed Morley authored
Found by diffing the published buildpack archives and looking at the git log to see what changed. It looks like the v108 entry was accidentally added in #405, when the release being published there was actually v107. The setuptools update mentioned there never happened, since the `SETUPTOOLS_VERSION` variable was found to be unused and instead removed.
-
- 05 Sep, 2017 7 commits
-
-
Kenneth Reitz authored
* fixed the bug for pypy-5.8.0 * update changelog Signed-off-by:
-
Kenneth Reitz authored
* fixed the bug for pypy-5.8.0 * update changelog Signed-off-by:
-
Kenneth Reitz authored
-
Kenneth Reitz authored
-
Kenneth Reitz authored
* Update README.md * Update README.md * Update README.md
-
Ed Morley authored
Previously the contents of the file being searched was not output, making it hard to know how to fix a test so that it would pass. Before: ``` $ make test-heroku-16 ... testCffi ASSERT:Expected </tmp/shunit.ayVGAO/tmp/output.6gMs/stdout> to contain <ZZZZZZZ> testPylibmc ``` After: ``` $ make test-heroku-16 ... testCffi ASSERT:Expected </tmp/shunit.FXWeuI/tmp/output.7Vfx/stdout> to contain <ZZZZZZZ> ! Warning: Your application is missing a Procfile. This file tells Heroku how to run your application. ! Learn more: https://devcenter.heroku.com/articles/procfile -----> Installing python-3.6.2 -----> Installing pip -----> Installing requirements with pip Collecting cffi (from -r /tmp/testBoLG0/requirements.txt (line 1)) Downloading cffi-1.10.0-cp36-cp36m-manylinux1_x86_64.whl (406kB) Collecting pycparser (from cffi->-r /tmp/testBoLG0/requirements.txt (line 1)) Downloading pycparser-2.18.tar.gz (245kB) Installing collected packages: pycparser, cffi Running setup.py install for pycparser: started Running setup.py install for pycparser: finished with status 'done' Successfully installed cffi-1.10.0 pycparser-2.18 testPylibmc ```
-
Ed Morley authored
* NLTK support: Update test to use multiple corpora So that the incorrect handling of multiple IDs seen in #444 would have been caught. Also switches to some of the smaller corpora, to reduce time spent downloading during tests (see sizes on http://www.nltk.org/nltk_data/). * NLTK support: Fix passing of multiple corpora identifiers As part of fixing the shellcheck warnigns in #438, double quotes had been placed around `$nltk_packages` passed to the `nltk.downloader`, which causes multiple identifiers to be treated as though it were just one identifier that contains spaces. The docs for the shellcheck warning in question recommend using arrays if the intended behaviour really is to split on spaces: https://github.com/koalaman/shellcheck/wiki/SC2086#exceptions As such, `readarray` has been used, which is present in bash >=4. The `[*]` array form is used in the log message, to prevent shellcheck warning SC2145, whereas `[@]` is used when passed to `nltk.downloader` to ensure the array elements are unpacked as required. Note: Both before and after this fix, using anything but unix line endings in `nltk.txt` will also cause breakage.
-
