-
Notifications
You must be signed in to change notification settings - Fork 910
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
Explore how other (meta-)packages handle dependencies #1777
Comments
Since we're not experts on this subject, maybe it's worth posting a detailed issue to https://github.com/pypa/packaging.python.org/issues, because they may be aware of best practices/examples or at least have an opinion. |
I just thought of another example-- |
We will not further pursue this approach for now as it seems like overkill to make Kedro into a metapackage structure. Further details and discussion can be seen under #1758. |
Copying relevant parts from #1758...
Maybe there is a whole different way of handling the
kedro
vs.kedro-datasets
split which would resolve the question of dependencies, what a user shouldpip install
, how to handle the namespace, etc. e.g. @deepyaman suggested akedro
metapackage in whichkedro-framework
andkedro-datasets
are both namespaced packages underneath that.We don’t need to commit to implementing the
kedro-framework
split now if we don’t want to, but I think it would be good to get a feeling for whether this a route we might want to go down in future because it influences our current decision on how to handlekedro-datasets
. e.g. it might convince us thatpip install kedro[pandas.CSVDataSet]
is good or bad.The text was updated successfully, but these errors were encountered: