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

Exclude Cassandra for Python 3.12 #38050

Merged
merged 1 commit into from
Mar 11, 2024

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Mar 11, 2024

We need to exclude Cassandra separately, in order to make sure that cassandra drivers are not installed in the Python 3.12 image when preparing it from the main branch.

Generally speaking the dependencies are cached from the main branch when image is built, which means that the resulting image will still have cassandra driver even if we remove it in final pyproject.toml.

The way how to get rid of it is two fold:

  1. add the exclusion to main
  2. after it is merged, increase the EPOCH number in the Dockerfile.ci
    in the PR that adds Python 3.12 compatibility

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

We need to exclude Cassandra separately, in order to make sure
that cassandra drivers are not installed in the Python 3.12 image
when preparing it from the main branch.

Generally speaking the dependencies are cached from the main branch
when image is built, which means that the resulting image will still
have cassandra driver even if we remove it in final pyproject.toml.

The way how to get rid of it is two fold:

1) add the exclusion to main
2) after it is merged, increase the EPOCH number in the Dockerfile.ci
   in the PR that adds Python 3.12 compatibility
@potiuk
Copy link
Member Author

potiuk commented Mar 11, 2024

This one MUST be merged before we do final check on #36755 - otherwise cached image will still contain cassandra driver.

@potiuk potiuk merged commit ac5f720 into apache:main Mar 11, 2024
84 of 85 checks passed
@potiuk potiuk deleted the add-cassandra-exclusion-for-python-3-12 branch March 11, 2024 20:37
drajguru pushed a commit to drajguru/airflow that referenced this pull request Mar 14, 2024
We need to exclude Cassandra separately, in order to make sure
that cassandra drivers are not installed in the Python 3.12 image
when preparing it from the main branch.

Generally speaking the dependencies are cached from the main branch
when image is built, which means that the resulting image will still
have cassandra driver even if we remove it in final pyproject.toml.

The way how to get rid of it is two fold:

1) add the exclusion to main
2) after it is merged, increase the EPOCH number in the Dockerfile.ci
   in the PR that adds Python 3.12 compatibility
@ephraimbuddy ephraimbuddy added the changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..) label Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:providers changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..) provider:apache-cassandra
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants