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

Update Heroku instructions in README #188

Merged
merged 1 commit into from
Feb 7, 2025
Merged

Update Heroku instructions in README #188

merged 1 commit into from
Feb 7, 2025

Conversation

edmorley
Copy link
Contributor

@edmorley edmorley commented Sep 7, 2024

Since Heroku's Python builds now use --enable-shared (for Python 3.10 and newer), so use of custom builds or a custom buildpack is no longer required - since everything now works with the official buildpack.

See:
heroku/heroku-buildpack-python#1320
https://github.com/heroku/heroku-buildpack-python/blob/928d0c593f6b6def16d6ad8451f56a997760eace/builds/build_python_runtime.sh#L117-L133

In addition the Python buildpack now supports the .python-version file (and recommends it over runtime.txt):
https://devcenter.heroku.com/changelog-items/3005

@@ -235,9 +209,6 @@ The Python bootstrapping process will appear in the log first, followed by the R
and so on. PyCall should now be able to successfully call Python functions from
within the Heroku environment.

NB It is also possible to specify buildpacks within Docker images on Heroku.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This removal is since the Heroku container deploy feature now only supports plain Dockerfile deploys, and not the previous experimental heroku.yml + buildpacks feature.

Since Heroku's Python builds now use `--enable-shared` (for Python 3.10 and newer), so use of custom builds or a custom buildpack is no longer required.

See:
heroku/heroku-buildpack-python#1320
https://github.com/heroku/heroku-buildpack-python/blob/928d0c593f6b6def16d6ad8451f56a997760eace/builds/build_python_runtime.sh#L117-L133

In addition the Python buildpack now supports the `.python-version` file (and recommends it over `runtime.txt`):
https://devcenter.heroku.com/changelog-items/3005
@edmorley
Copy link
Contributor Author

I've rebased on main + also replaced the runtime.txt references to use .python-version (now that Heroku supports it, and recommends it over runtime.txt: https://devcenter.heroku.com/changelog-items/3005).

@mrkn I don't suppose you could mark the pending GitHub Actions workflow as allowed, so it can run? :-)

@edmorley
Copy link
Contributor Author

edmorley commented Feb 6, 2025

@mrkn Please could this be merged? The current docs are broken (the tag no longer exists etc).

@mrkn mrkn merged commit 64077b6 into mrkn:master Feb 7, 2025
@edmorley edmorley deleted the patch-1 branch February 7, 2025 19:45
@edmorley
Copy link
Contributor Author

edmorley commented Feb 7, 2025

Thank you!

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

Successfully merging this pull request may close these issues.

2 participants