[DEV-10804] Removed unused imports flagged by flake8 #4049
Merged
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
…ot yet been moved to the current sprint. However, I implemented the changes so travis build could proceed to the unit tests where I can see the spark/unit tests that are failing.
ghost
approved these changes
Mar 20, 2024
Base automatically changed from
dev-10756-update-config-files
to
dev-10645-python-upgrade-3.10
March 20, 2024 20:17
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.
Removed unused imports flagged by flake8. This ticket has not yet been moved to the current sprint. However, I implemented the changes so travis build could proceed to the unit tests where I can see the spark/unit tests that are failing.
Description:
Flake8 tests were not passing in Travis due to a list of unused imports across various files. Those unused imports were removed.
Technical details:
The technical details for the knowledge of other developers. Any detailed caveats or specific deployment steps should be outlined here.
Requirements for PR merge:
Area for explaining above N/A when needed: