build: remove unused dependencies from requirements.txt
#5179
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
|
We'll want to keep an eye on next deploy and crons to ensure everything is kosher, but given builds are succeeded and were tested, I feel comfortable 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.
In my analysis of requirements.txt, I found out that these are unused.
We will be testing it whether that is actually the case and there aren't any hidden/indirect usage. I tried building it locally and it seems to work.
Ref: #5162 (comment)
Also, I found out even if we do not include them in the requirements.txt, they will be installed as they are indirect dependencies of some other packages:
Closes #
Technical
Testing
Screenshot
Stakeholders
@cdrini @mekarpeles