- May 01, 2018
-
-
Terence Lee authored
-
- Apr 20, 2018
-
-
Kenneth Reitz authored
-
- Apr 17, 2018
-
-
Kenneth Reitz authored
* freeze pip version, upon installation Signed-off-by:
Kenneth Reitz <me@kennethreitz.org> * use PIP_UPDATE environment variable Signed-off-by:
-
- Mar 20, 2018
-
-
Kenneth Reitz authored
-
- Mar 19, 2018
-
-
Kenneth Reitz authored
Signed-off-by: -
Yury V. Zaytsev authored
* Since pipenv is being pinned now, output pinned version in steps Signed-off-by:
Yury V. Zaytsev <yury.zaytsev@moneymeets.com> * Update README.md example output to match new reality Signed-off-by:
-
- Mar 14, 2018
-
-
Kenneth Reitz authored
-
Kenneth Reitz authored
-
Kenneth Reitz authored
-
Kenneth Reitz authored
-
Kenneth Reitz authored
* default to user python path for collectstatic runs Signed-off-by:
-
Kenneth Reitz authored
* metrics Signed-off-by:
-
- Mar 07, 2018
-
-
Kenneth Reitz authored
Signed-off-by: -
Kenneth Reitz authored
Signed-off-by: -
Kenneth Reitz authored
Signed-off-by: -
Kenneth Reitz authored
Signed-off-by: -
Kenneth Reitz authored
Signed-off-by: -
Kenneth Reitz authored
Signed-off-by: -
Kenneth Reitz authored
Signed-off-by: -
Kenneth Reitz authored
Signed-off-by:
-
- Mar 06, 2018
-
-
Kenneth Reitz authored
Signed-off-by: -
Kenneth Reitz authored
Signed-off-by: -
Kenneth Reitz authored
-
- Mar 03, 2018
-
-
Kenneth Reitz authored
* Update pipenv-python-version * use latest versions in pipenv script Signed-off-by:
-
- Mar 02, 2018
-
-
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
-
- Feb 17, 2018
-
-
Eugene Pakhomov authored
* Add support for PIP_EXTRA_INDEX_URL * Add support for PIP_EXTRA_INDEX_URL for Pipenv
-
- Jan 16, 2018
-
-
Kenneth Reitz authored
* initial stab at pipenv --dev support * test installation output * locale fix * refactor * fix typo * fix typo * ellipsis * polish
-
- Dec 18, 2017
-
-
Kenneth Reitz authored
* mcount pipenv * more mcount for pip * shellcheck compliance * fix typo Signed-off-by:
-
- Nov 22, 2017
-
-
Josh Friend authored
-
- Nov 15, 2017
-
-
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
-
- Sep 26, 2017
-
-
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:
-
- Sep 25, 2017
-
-
Kenneth Reitz authored
* improvements to pipenv Signed-off-by:
-
- Sep 08, 2017
-
-
Kenneth Reitz authored
* only do this on heroku-16 * history Signed-off-by:
-
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.
-
- Sep 05, 2017
-
-
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:
-
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.
-
