Deprecate buildpack now that the Python buildpack supports uv #4
Description
Hi!
Thank you for much for contributing a buildpack to allow people to use uv prior to it being natively supported by Heroku's Python buildpack.
As you may have seen, we recently added native support for uv to both our classic Python buildpack and the Python CNB:
https://devcenter.heroku.com/changelog-items/3238
The PR for adding support to the uv buildpack can be seen here:
heroku/heroku-buildpack-python#1791
We'd like to encourage users of heroku-uv-buildpack to migrate to the native uv support in the Python buildpack, since:
- it installs dependencies using uv, rather than using pip from an exported requirements file (so is faster and will prevent divergences from local development environments where uv is being used directly)
- we can more easily offer ongoing support (eg keeping uv versions up to date etc)
We've mentioned some migration instructions in our changelog post, but it may also help if we could add a deprecation message to this buildpack's build log output - similar to what we did for the third-party Poetry buildpack back when we added support for Poetry? (See moneymeets/python-poetry-buildpack#76)
I can open a PR for that if it's of help?