refactor: Prune unused dependencies#114
refactor: Prune unused dependencies#114kirillbobyrev wants to merge 1 commit intofacebookresearch:mainfrom
Conversation
|
Hi @kirillbobyrev! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Python package requirements for this repository likely contain a snapshot of all installed packages in the environment, but most of the dependencies in
requirements.txt(and sibling files) are unused. They can be pruned, which makes the dependency tree much leaner and alleviates the pressure from the Python package management resolver.Additionally, some dependencies (like
kaolin) are heavyweight but aren't actually used enough, so simple assertions are sufficient.