-
Notifications
You must be signed in to change notification settings - Fork 442
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
Remove some deprecated features #2926
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
9334e5e
to
a00e385
Compare
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.
Minors only, feel free to ignore and merge
@@ -67,54 +59,6 @@ def test_environment_is_singleton(): | |||
assert Environment() is Environment() | |||
|
|||
|
|||
def test_step_is_running(): |
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.
Why this is deleted?
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 deleted the entire functionality of the StepEnvironment
which was an old/unused class that was just duplicating information of the StepContext
.
The current way to check whether we're in a step is to check whether get_step_context
works, do you think it's still worth it to have that as a boolean on this class and add the test back in?
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.
@@ -625,7 +625,7 @@ def deploy_mlstacks_stack( | |||
declare("Stack successfully deployed.") | |||
|
|||
if not no_import_stack_flag: | |||
declare(f"Importing stack '{stack_name}' into ZenML...") | |||
declare(f"Importing stack '{stack_name}' into ZenML..") |
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.
😄
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 have no idea how this ended up in there, must have been some search and replace :D
Describe changes
Removes a few features that have been deprecated for a long time:
Output
andBaseParameters
classesStepEnvironment
zenml.steps.external_artifact.ExternalArtifact
)Pre-requisites
Please ensure you have done the following:
develop
and the open PR is targetingdevelop
. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.Types of changes