Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate and eventually sunset runtime.txt support #275

Open
edmorley opened this issue Sep 17, 2024 · 0 comments
Open

Deprecate and eventually sunset runtime.txt support #275

edmorley opened this issue Sep 17, 2024 · 0 comments

Comments

@edmorley
Copy link
Member

edmorley commented Sep 17, 2024

As of #272, the buildpack now supports the .python-version file for configuring the Python version.

The .python-version file is superior in several ways:

  • it is commonly supported/used by other tools (unlike runtime.txt, which is Heroku proprietary)
  • it supports the major Python version syntax (eg 3.X rather than 3.X.Y), so supports automatic security updates without needing to manually bump the patch version each time.

As such, we should deprecate runtime.txt support in the CNB, and then eventually remove support from the CNB entirely.

Note: For the classic buildpack, we'll be also adding .python-version support there soon (which I'd like to do before deprecating runtime.txt in the CNB). However, for the classic buildpack we'll never want to fully remove runtime.txt support - and instead only deprecate it - to at least encourage most users to migrate over before they eventually migrate to the CNB (xref heroku/heroku-buildpack-python#1642).

GUS-W-16878239.
GUS-W-16878263.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant