-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Exclude 2.3.3 of pymssql #48604
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 2.3.3 of pymssql #48604
Conversation
The release 2.3.3 of pymssql is broken because it does not have neither sdist nor linux wheels - so it cannot be installed. Issue tracked in: pymssql/pymssql#927
amoghrajesh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Woops! I think they will fix it since there's an issue!
Huge |
|
But their plpeline might not be prepared for updating missing files and they might need to release a new version. |
IAC, safe to exclude, yes! |
The release 2.3.3 of pymssql is broken because it does not have neither sdist nor linux wheels - so it cannot be installed. Issue tracked in: pymssql/pymssql#927
The release 2.3.3 of pymssql is broken because it does not have neither sdist nor linux wheels - so it cannot be installed. Issue tracked in: pymssql/pymssql#927
The release 2.3.3 of pymssql is broken because it does not have neither sdist nor linux wheels - so it cannot be installed. Issue tracked in: pymssql/pymssql#927
The release 2.3.3 of pymssql is broken because it does not have neither sdist nor linux wheels - so it cannot be installed. Issue tracked in: pymssql/pymssql#927
The release 2.3.3 of pymssql is broken because it does not have neither sdist nor linux wheels - so it cannot be installed.
Issue tracked in: pymssql/pymssql#927
^ 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.