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

Allow python 3.12 for the breeze release commands #42936

Merged
merged 1 commit into from
Oct 11, 2024

Conversation

ashb
Copy link
Member

@ashb ashb commented Oct 11, 2024

I'm not 100% sure why we added this check in the first place, but it doesn't
seem to be needed anymore (I've tested things locally with this removed and it
all seems to behave itself)

I'm not 100% sure why we added this check in the first place, but it doesn't
seem to be needed anymore (I've tested things locally with this removed and it
all seems to behave itself)
@ashb ashb merged commit 57aeb34 into main Oct 11, 2024
54 checks passed
@ashb ashb deleted the allow-py3.12-release-commands branch October 11, 2024 10:11
@potiuk
Copy link
Member

potiuk commented Oct 11, 2024

It's just a matter of looking it up in git blame.

Actually this is not really good idea for now (Provider's release manager's releasing providers should not use Python 3.12). it's all visible in detail in history of those changed lines.

What can actually be removed now is the 3.9 check (because we do not use Python 3.8 any more and python 3.8 produced non-reproducible builds as explained in comments and in #37401). \

Python 3.12 was excluded (additionally) here #37615 because some of our provider packages did not support 3.12 and as of recently as part of release process we are building .sdist packages and they cannot be build for packages that do not support Python 3.12. Currently apache-beam does not support Python 3.12 yet (mostly because they embedded dill version that breaks our PythonVirtualenvOperator as explained in #41990 and we cannot enabvle it until apache/beam#32617 is fixed.

But yeah. It makes no sense to block 3.12 usage for everyone, it might be enough to remove it for providers release command only. I will correct it.

potiuk added a commit to potiuk/airflow that referenced this pull request Oct 11, 2024
Follow up after apache#42766 and apache#42936.

* We do not have to check for minimum Python version for Python 3.9
  any more (as we do not support 3.8 any more)
* While Python 3.12 is not yet fully supported by Apache Beam, we
  should still not allow it for releasing providers, but all other
  commands should support Python 3.12
* When you had pre-commit installed with Python 3.8 before, various
  errors might appear when running pre-commit. Troubleshooting
  was added quoting the errors and explaining what to do.
@potiuk
Copy link
Member

potiuk commented Oct 11, 2024

Better fix in #42944

potiuk added a commit that referenced this pull request Oct 11, 2024
Follow up after #42766 and #42936.

* We do not have to check for minimum Python version for Python 3.9
  any more (as we do not support 3.8 any more)
* While Python 3.12 is not yet fully supported by Apache Beam, we
  should still not allow it for releasing providers, but all other
  commands should support Python 3.12
* When you had pre-commit installed with Python 3.8 before, various
  errors might appear when running pre-commit. Troubleshooting
  was added quoting the errors and explaining what to do.
@ashb
Copy link
Member Author

ashb commented Oct 12, 2024

It's just a matter of looking it up in git blame.

Not really, not to me anyway -- I found the PR #37615 before opening this but that didn't actually give me any further clues as to what the actual problem using Py 3.12 was.

kunaljubce pushed a commit to kunaljubce/airflow that referenced this pull request Oct 13, 2024
I'm not 100% sure why we added this check in the first place, but it doesn't
seem to be needed anymore (I've tested things locally with this removed and it
all seems to behave itself)
kunaljubce pushed a commit to kunaljubce/airflow that referenced this pull request Oct 13, 2024
Follow up after apache#42766 and apache#42936.

* We do not have to check for minimum Python version for Python 3.9
  any more (as we do not support 3.8 any more)
* While Python 3.12 is not yet fully supported by Apache Beam, we
  should still not allow it for releasing providers, but all other
  commands should support Python 3.12
* When you had pre-commit installed with Python 3.8 before, various
  errors might appear when running pre-commit. Troubleshooting
  was added quoting the errors and explaining what to do.
pavansharma36 pushed a commit to pavansharma36/airflow that referenced this pull request Oct 14, 2024
I'm not 100% sure why we added this check in the first place, but it doesn't
seem to be needed anymore (I've tested things locally with this removed and it
all seems to behave itself)
pavansharma36 pushed a commit to pavansharma36/airflow that referenced this pull request Oct 14, 2024
Follow up after apache#42766 and apache#42936.

* We do not have to check for minimum Python version for Python 3.9
  any more (as we do not support 3.8 any more)
* While Python 3.12 is not yet fully supported by Apache Beam, we
  should still not allow it for releasing providers, but all other
  commands should support Python 3.12
* When you had pre-commit installed with Python 3.8 before, various
  errors might appear when running pre-commit. Troubleshooting
  was added quoting the errors and explaining what to do.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants