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

Fix for compatibility with Kedro 0.18.4 onwards #22

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

Prospect-Zubin
Copy link

Updates to allow integration with kedro 0.18.4 > onwards which uses OmegaConfigLoader which replaced the legacy ConfigLoader and TemplatedConfigLoader previously used. Updates also allow for backwards integration for versions of kedro <= 0.18.4.

Updates also added user flexibility for choice of docker image platform architecture which allows for multi-architecture docker images.

As a result of the codebase changes updates to the affected unit tests were made.

This is my first PR for a public codebase so any feedback or comments is appreciated :)

…megaConfigLoader which replaced the legacy ConfigLoader and TemplatedConfigLoader previously used. Updates also allow for backwards integration for versions of kedro <= 0.18.4.

Updates also added user flexibility for choice of docker image platform architecture which allows for multi-architecture docker images.

As a result of the codebase changes updates to the affected unit tests were made.
Comment on lines +11 to +13
import kedro
from kedro.framework.session import KedroSession
from packaging import version

Choose a reason for hiding this comment

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

You might want to use importlib.metadata instead of relying on packaging.version and kedro.__version__ https://docs.python.org/3.9/library/importlib.metadata.html#metadata

Copy link
Author

Choose a reason for hiding this comment

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

Sure happy to make that change. What is the benefit of doing it that way rather than using packaging.version?

Choose a reason for hiding this comment

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

Using packaging.version might be unavoidable if you want to parse it. The key is how to obtain the currently installed version, and importlib.metadata is the canonical way I'd say. See pallets/flask#5230

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants