-
Notifications
You must be signed in to change notification settings - Fork 3.6k
add freeze for development and full range for install #12994
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Carlos Mocholí <carlossmocholi@gmail.com>
awaelchli
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome!
|
|
||
|
|
||
| def _load_requirements(path_dir: str, file_name: str = "requirements.txt", comment_char: str = "#") -> List[str]: | ||
| def _load_requirements( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you explain what the core change is here, on a high level? I'm not exactly sure what it does or when it is used
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when you install PL as a python package our requirements listed in files need to be loaded and passed to the setup function... till now we just dropped all comments and HTTP links, but now we also remove all upper bound version limitations unless it is intended (the commend after package includes word strict)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay I see. So basically if the requirement says x >= 1.5, <1.7, we will install as if x >= 1.5. Sounds good! Do we actually have examples where the comment includes "strict"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay I see. So basically if the requirement says
x >= 1.5, <1.7, we will install as if x >= 1.5
the pattern for replacement is <= not < as the dependabot would list the last feasible version
Do we actually have examples where the comment includes "strict"?
not yet as we do not have such case yet :/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is nice! Please correct me if I'm wrong, but with this logic, we don't need to change anything in the requirements files (i.e., we don't need to unpin the upper-bounded versions) when releasing, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kaushikb11 ^^
|
|
||
|
|
||
| def _load_requirements(path_dir: str, file_name: str = "requirements.txt", comment_char: str = "#") -> List[str]: | ||
| def _load_requirements( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay I see. So basically if the requirement says x >= 1.5, <1.7, we will install as if x >= 1.5. Sounds good! Do we actually have examples where the comment includes "strict"?
for more information, see https://pre-commit.ci
akihironitta
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change in setup_tools.py is very interesting 🚀
| rich>=10.2.2,!=10.15.* | ||
| matplotlib>3.1, <=3.5.1 | ||
| torchtext>=0.9.*, <=0.12.0 | ||
| omegaconf>=2.0.5, <=2.1.* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
noob question: How is it different from specifying the exact version? e.g. <=2.1.* vs. <=2.1.2
Not sure why some use .* and others use exact versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.* includes all bugfixes...
<=2.1.* is the same as <2.2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should all upper bounds be written that way then?
For example,
- matplotlib>3.1, <=3.5.1
- torchtext>=0.9.*, <=0.12.0
+ matplotlib>3.1, <=3.5.*
+ torchtext>=0.9.*, <=0.12.*There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's nothing critical, but I'm just curious why some are written so while others aren't.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can convert them to a specific version :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO, we should have specific versions for all packages to further reduce the possibility of something getting broken. (meaning we shouldn't use *.)
Co-authored-by: Akihiro Nitta <nitta@akihironitta.com>
| horovod>=0.21.2,!=0.24.0 # no need to install with [pytorch] as pytorch is already installed | ||
| hivemind>=1.0.1; sys_platform == 'linux' | ||
| # no need to install with [pytorch] as pytorch is already installed | ||
| horovod>=0.21.2,!=0.24.0, <=0.24.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment will go next to horovod.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it was too long line, but yes, we can move it back...
Borda
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
->
Co-authored-by: Carlos Mocholí <carlossmocholi@gmail.com> Co-authored-by: Akihiro Nitta <nitta@akihironitta.com>
Co-authored-by: Carlos Mocholí <carlossmocholi@gmail.com> Co-authored-by: Akihiro Nitta <nitta@akihironitta.com>
Co-authored-by: Carlos Mocholí <carlossmocholi@gmail.com> Co-authored-by: Akihiro Nitta <nitta@akihironitta.com>
What does this PR do?
Closes #12383
set all max versions of today's latest released version and define dependabot to open PR when a new release appears...
in setup add logic for removing this upper bound unless it is commented in as strict
Before submitting
PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 🙃
cc @carmocca @akihironitta @Borda @tchaton @rohitgr7