Add sqlalchemy-spanner limitation for broken 1.12.0 release #51393
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
potiuk
force-pushed
the
exclude-sqlalchemy-spanner-for-highest-resolution-in-pypi
branch
2 times, most recently
from
c143ad6 to
401f81f
Compare
When constraints are calculated, we should termporarily exclude the sqlalchemy-spanner from the install command until they fix the problem where 1.12.0 was relesed without .whl files. Tracked in googleapis/python-spanner-sqlalchemy#682
potiuk
force-pushed
the
exclude-sqlalchemy-spanner-for-highest-resolution-in-pypi
branch
from
401f81f to
1109384
Compare
potiuk
deleted the
exclude-sqlalchemy-spanner-for-highest-resolution-in-pypi
branch
Lee-W
pushed a commit
to astronomer/airflow
that referenced
this pull request
Jun 5, 2025
…1393) When constraints are calculated, we should termporarily exclude the sqlalchemy-spanner from the install command until they fix the problem where 1.12.0 was relesed without .whl files. Tracked in googleapis/python-spanner-sqlalchemy#682
potiuk
added a commit
that referenced
this pull request
Jun 5, 2025
…se (#51393) (#51432) When constraints are calculated, we should termporarily exclude the sqlalchemy-spanner from the install command until they fix the problem where 1.12.0 was relesed without .whl files. Tracked in googleapis/python-spanner-sqlalchemy#682 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
kaxil
pushed a commit
that referenced
this pull request
Jun 6, 2025
…se (#51393) (#51432) When constraints are calculated, we should termporarily exclude the sqlalchemy-spanner from the install command until they fix the problem where 1.12.0 was relesed without .whl files. Tracked in googleapis/python-spanner-sqlalchemy#682 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
sanederchik
pushed a commit
to sanederchik/airflow
that referenced
this pull request
Jun 7, 2025
…1393) When constraints are calculated, we should termporarily exclude the sqlalchemy-spanner from the install command until they fix the problem where 1.12.0 was relesed without .whl files. Tracked in googleapis/python-spanner-sqlalchemy#682
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When constraints are calculated, we should termporarily exclude the sqlalchemy-spanner from the install command until they fix the problem where 1.12.0 was relesed without .whl files.
Tracked in googleapis/python-spanner-sqlalchemy#682
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.