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

Install the specified python version found in pyproject.toml #2

Closed
paxcodes opened this issue Mar 3, 2020 · 4 comments · Fixed by #4
Closed

Install the specified python version found in pyproject.toml #2

paxcodes opened this issue Mar 3, 2020 · 4 comments · Fixed by #4
Assignees

Comments

@paxcodes
Copy link

paxcodes commented Mar 3, 2020

Since poetry currently does not export runtime.txt Heroku installs a different Python version than what is specified in pyproject.toml.

@zyv
Copy link
Contributor

zyv commented Mar 3, 2020

@paxcodes that’s correct, thank you for the heads up. We have historically committed runtime.txt into our repos, that’s why we are not having this problem.

However, now that we have written a buildpack, we could just export runtime.txt in the buildpack and agree internally, that we are going to specify minors in pyproject.toml.

@marns93 , @mm-matthias what do you think?

@zyv zyv assigned zyv and marns93 and unassigned zyv Mar 3, 2020
@mm-matthias
Copy link
Contributor

@zyv There are several options:

  1. Always write runtime.txt in the buildpack, possibly overwriting an existing runtime.txt. Requires pyproject.toml to contain the minor version number.
  2. Always write runtime.txt in the buildpack. Raise an error if there is already an existing runtime.txt. Requires pyproject.toml to contain the minor version number.
  3. If there is an existing runtime.txt, do not overwrite it in the generator. Optionally check if the version number in pyproject.toml matches the version in runtime.txt.

For our own purposes I'd go with option 2) as this makes sure the heroku and pyproject.toml versions of python always match.

What are your preferences @paxcodes ?

@paxcodes
Copy link
Author

paxcodes commented Mar 3, 2020 via email

@zyv
Copy link
Contributor

zyv commented Mar 3, 2020

Let's go for raising an exception, otherwise we might end up with discrepancies we'll find out about only too late @mm-matthias & @marns93.

felix11h pushed a commit that referenced this issue Sep 2, 2022
Co-authored-by: Dustin Chilson <dustin.chilson@salespad.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

4 participants