Fix PyPI publication by updating snowflake-connector-python #657
Conversation
This file contains 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
|
This pull request has been linked to Shortcut Story #21491: Unable to publish to PyPI due to oscrypto. |
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
Codecov ReportAll modified and coverable lines are covered by tests ✅ see 31 files with indirect coverage changes 📢 Thoughts on this report? Let us know!. |
alyiwang
approved these changes
Nov 3, 2023
mars-lan
deleted the
marslan/sc-21491/unable-to-publish-to-pypi-due-to-oscrypto
branch
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.
🤔 Why?
We were unable to publish to PyPI due to the workaround suggested by wbond/oscrypto#78 (comment).
🤓 What?
Now that the latest version of https://github.com/snowflakedb/snowflake-connector-python has moved away from
oscrypt, we can simply update and remove the workaround.🧪 Tested?
Verified against a production instance.