Releases: heroku/heroku-buildpack-python
Releases · heroku/heroku-buildpack-python
v269
- The Python 3.13 version alias now resolves to Python 3.13.1. (#1712)
- The Python 3.12 version alias now resolves to Python 3.12.8. (#1712)
- The Python 3.11 version alias now resolves to Python 3.11.11. (#1712)
- The Python 3.10 version alias now resolves to Python 3.10.16. (#1712)
- The Python 3.9 version alias now resolves to Python 3.9.21. (#1712)
v268
v267
v266
- Added a warning when the files for multiple package managers are found. In the future this warning will become an error. (#1692)
- Updated the build log message shown when installing dependencies to include the package manager command being run. (#1689)
- Changed test dependency installation on Heroku CI to now install
requirements.txtandrequirements-test.txtin a singlepip installinvocation rather than separately. This allows pip's resolver to resolve any version conflicts between the two files. (#1689) - Improved the error messages and buildpack metrics for package manager related failures. (#1689)
- Improved the build log output, error messages and buildpack failure metrics for the NLTK downloader feature. (#1690)
v265
v264
v263
- Fixed cache handling so that it now also discards the cache when the package manager (or its version) changes. (#1679)
- Improved the build log output shown when restoring or discarding the cache. For example, if the cache was invalidated all reasons are now shown. (#1679)
- Stopped performing unnecessary cache file copies when the cache is due to be invalidated. This required moving the cache restoration step to after the
bin/pre_compilehook runs. (#1679) - Fixed cache restoration in the case where an app's
requirements.txtwas formerly a symlink. (#1679) - Added buildpack metrics for the status of the cache and duration of cache restoration/saving. (#1679)
v262
v261
- Added support for configuring the Python version using a
.python-versionfile. Both the3.Nand3.N.Nversion forms are supported (the former is recommended). The existingruntime.txtfile will take precedence if both files are found, however, we recommend switching to.python-versionsince it is more commonly supported in the Python ecosystem. (#1664) - Added support for specifying only the Python major version in
runtime.txtinstead of requiring the full Python version (for examplepython-3.Ninstead ofpython-3.N.N). (#1664)