-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Use pyproject.toml instead of requirements.txt #1210
Comments
@bolinocroustibat Hi! I can't wait until things are more standardised around The recent changes in pip use There are discussions about using I'll close this out for now pending future PEPs and pip support (also by the time that happens, we'll have likely migrated from this classic Heroku buildpack API v2 buildpack, to the new Cloud Native Buildpacks in another repo). |
Hello! So the only way to deploy apps developed with tools like pdm on heroku is still to export the dependencies to |
@baggiponte Hi! The suggested approaches in #1341 (comment) are still the best way to use PDM. |
thank you for the reply! (Also, where can I find updates for the current status of the cloud native buildpack implementation?) |
The CNB is being developed here: |
Could it use the now standard PEP 518 / PEP 621
pyproject.toml
by default, and fallback torequirements.txt
if not present?AFAIK
pip install pyproject.toml
instead ofpip install -r requirements.txt
is now fully supported by pip.(I know there is a Poetry buildpack, but since pyproject.toml is the new standard, I don't think it should be related to Poetry, neither export to old requirements.txt like the Poetry buildpack does)
The text was updated successfully, but these errors were encountered: