Bump pymssql version to 2.3.5 #52307
Merged
+1
−7
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
There is a problem with 2.3.4 that the .whl files for MacOS are broken / missing and when installing with Python 3.10 on MacOS, pymssql installation fails. Since this is only pymssql, we can easily bump it to 2.3.5 to avoid it - it is the latest version installed anyway in main now.
gopidesupavan
approved these changes
Jun 26, 2025
eladkal
approved these changes
Jun 26, 2025
|
Images build and tested with it already .. merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There is a problem with 2.3.4 that the .whl files for MacOS are broken / missing and when installing with Python 3.10 on MacOS, pymssql installation fails. Since this is only pymssql, we can easily bump it to 2.3.5 to avoid it - it is the latest version installed anyway in main now.
^ 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.