Skip to content
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

Dependency cleanup and Python 3.12 support #2953

Merged
merged 96 commits into from
Sep 3, 2024

Conversation

bcdurak
Copy link
Contributor

@bcdurak bcdurak commented Aug 27, 2024

Describe changes

Major changes

  • Cleaning up the dependencies:
    • Removed click-params, httplib2, pyparsing as main dependencies.
    • Moved secure to the server extra
    • Separated numpy and pandas to implementations to their own integrations.
    • Added a limited version of maison to solve a problem with the yamlfix installation.
    • Upgraded pydantic to 2.8.*
  • Upgrading zenml to Python 3.12. The new version is also added to all relevant CI tests.

Minor changes

  • Minor formatting/linting changes in some of the integrations.
  • Reworked one of the unit tests to use the PydanticMaterializer instead of the PandasMaterializer.
  • Limited the pandas version in the deepchecks integration to <2.1.0.
  • Added placeholder materializers for the PandasMaterializer and the NumpyMaterializer.
  • mlflow integration slightly reworked. The extra deployment option mlserver and mlserver-mlflow only installed <3.12 now.
  • Some of our examples use the package: skimage. Previously, we were able to access this package (for instance in mlflow and seldon example tests) because deepchecks was installed in the same environment and deepchecks required it (because we installed all the integration together). However, on 3.12, deepchecks integration is still not supported -> it is not installed -> there is no skimage -> mlflow and seldon example tests fail. The package itself is around 14 MB so I added it to the sklearn integration.

Related PRs

Remaining TODOs

  • Investigate if we should implement a migration script to change the materializer entries to newer paths.
  • Investigate Windows testing on 3.12.
  • Add warnings/errors for integrations that are not yet supported in 3.12..
  • Ignore the integration tests on 3.12 for integrations that are not yet supported in 3.12..
  • Revert the changes in the CI.
  • Create new versions of all templates.
  • Investigate httplib2 and pyparsing issue.

Pre-requisites

Please ensure you have done the following:

  • I have read the CONTRIBUTING.md document.
  • If my change requires a change to docs, I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
  • If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Other (add details above)

Copy link
Contributor

coderabbitai bot commented Aug 27, 2024

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

socket-security bot commented Aug 27, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
pypi/[email protected] None 0 45.6 kB dbatten4
pypi/[email protected] environment, eval, filesystem, network, shell, unsafe 0 5.32 MB abravalheri, dstufft, jaraco

🚮 Removed packages: pypi/[email protected]), pypi/[email protected]), pypi/[email protected]), pypi/[email protected]), pypi/[email protected])

View full report↗︎

@github-actions github-actions bot added internal To filter out internal PRs and issues enhancement New feature or request labels Aug 27, 2024
src/zenml/materializers/__init__.py Show resolved Hide resolved
src/zenml/integrations/deepchecks/__init__.py Outdated Show resolved Hide resolved
pyproject.toml Show resolved Hide resolved
@bcdurak
Copy link
Contributor Author

bcdurak commented Aug 28, 2024

Btw, @schustmi, this PR is still early in development. I was just using it to test things on the CI. Will update you as things move forward.

Copy link
Contributor

Classification template updates in examples/mlops_starter have been pushed.

Copy link
Contributor

@stefannica stefannica left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks good, but I had some nits and questions here and there.

Comment on lines +32 to +33
# TODO: Remove and add the extra back in
uv pip install $PIP_ARGS git+https://github.com/zenml-io/mlstacks.git@feature/upgrade-python-3.12
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remember to remove this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the reminder. I had to add one more of this to the small-checks workflow in the CI, unfortunately. We have to keep them until we can release a new version of mlstacks. I will keep this thread unresolved as a reminder to myself.

Copy link
Contributor Author

@bcdurak bcdurak Sep 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stefannica Just so you know, this is going to be a bit tricky as I can not remove these lines with this PR.

Right now, the changes that I made are not compatible with the latest release of mlstacks(0.9.0). If I remove them now and merge to develop, all the subsequent CI runs on other PRs branching off of develop will fail.

We can potentially release a new version of mlstacks as a solution but if we do that mlstacks will be broken until we release a new version of zenml. (There won't be any zenml versions which can work with this new mlstacks release.)

So, my proposal would be something like this:

  1. I merge this PR while keeping install-zenml-dev and small-checks pointing to my upgrade branch on the mlstacks repo.
  2. I create a follow-up PR which actually reverts them back.
  3. Just before we release a new version of zenml, we do the mlstacks release, merge the PR from point 2 and proceed with the release.

This needs to be communicated to the product team as well, I will take over that.

src/zenml/integrations/deepchecks/__init__.py Outdated Show resolved Hide resolved
Copy link
Contributor

@avishniakov avishniakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with the concerns raised by @stefannica. On top, I added a few minor comments.

pyproject.toml Outdated Show resolved Hide resolved
src/zenml/zen_stores/sql_zen_store.py Show resolved Hide resolved
Comment on lines +81 to +84
from zenml.zen_server.secure_headers import (
initialize_secure_headers,
secure_headers,
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice move 👍🏼

Copy link
Contributor

github-actions bot commented Sep 3, 2024

LLM Finetuning template updates in examples/llm_finetuning have been pushed.

Copy link
Contributor

github-actions bot commented Sep 3, 2024

E2E template updates in examples/e2e have been pushed.

Copy link
Contributor

github-actions bot commented Sep 3, 2024

NLP template updates in examples/e2e_nlp have been pushed.

Copy link
Contributor

github-actions bot commented Sep 3, 2024

Classification template updates in examples/mlops_starter have been pushed.

@bcdurak bcdurak merged commit 142f7f1 into develop Sep 3, 2024
4 checks passed
@bcdurak bcdurak deleted the feature/PRD-566-dependency-cleanup branch September 3, 2024 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change enhancement New feature or request internal To filter out internal PRs and issues run-slow-ci
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants