-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[App] Auto-upgrade / detect environment mis-match from the CLI #15434
Conversation
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.
Looks neat so far.
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.
LGTM !
@@ -37,6 +37,8 @@ | |||
if module_available("lightning_app.components.demo"): | |||
from lightning_app.components import demo # noqa: F401 | |||
|
|||
__package_name__ = "lightning_app".split(".")[0] |
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.
?
|
||
|
||
@pytest.mark.parametrize( | ||
"releases, current_version, newer_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.
how about dev version if it is installed from the source?
* Add auto-upgrade from the CLI and check for current env * No longer require `python -m` in docs * Tabs -> spaces * Ignore pre-releases * Test + docs (cherry picked from commit 555257a)
* Add auto-upgrade from the CLI and check for current env * No longer require `python -m` in docs * Tabs -> spaces * Ignore pre-releases * Test + docs (cherry picked from commit 555257a)
What does this PR do?
Adds utilities to the lightning app CLI to avoid the need for
python -m XXX
:Note: The test here is quite minimal for now as this can't be tested without mocking out all of the important pieces (at which point the test wouldn't catch anything)
Does your PR introduce any breaking changes? If yes, please list them.
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 🙃