Lock smart_open to v6.4.0 to fix unit-test and Python3.6 build failures. #47
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
LinZhihao-723
changed the title
kirkrodrigues
approved these changes
Mar 15, 2024
There was a problem hiding this comment.
How about:
Lock smart_open to v6.4.0 to fix unit-test and Python3.6 build failures. (#47)
LGTM |
LinZhihao-723
changed the title
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.
References
Description
smart-openhas released version 7.0.1. In this new version, they introduced__future__notations, which were not supported in Python3.6, thus causing the unit test failures. Also, it attempts to use the_FileLikeProxy__innerattributes ofzstd.ZstdCompressionWriter, which does not exist. Therefore, we will locksmart-opento an earlier version to avoid unit test failures.Validation performed