Fix requirements parsing and declare Python >= 3.9#2219
Fix requirements parsing and declare Python >= 3.9#2219SY-Jia06 wants to merge 1 commit intofacebookresearch:mainfrom
Conversation
|
Hi @SY-Jia06! 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! |
|
Small packaging fix, ready for review. No runtime changes. |
Motivation and Context
setup.pypreviously splitrequirements.txtverbatim, which includes comment lines. Those can be interpreted as invalid requirements duringpip install -e habitat-lab. This change filters comments/blank lines, updates the Python badge to 3.9, and declarespython_requires>=3.9for consistent packaging metadata.How Has This Been Tested
Not run (packaging metadata only).
Types of changes