-
Notifications
You must be signed in to change notification settings - Fork 909
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
Consider removal of project cli.py #2384
Comments
If you want to extend the run command with extra click inputs I think this is the only way. What I would like is if we go down the I think from a user point of view copy and pasting something that works is much less intimidating that creating a plugin. By that logic, I'd also be open to |
Currently it's the only way without writing a plugin, but how common actually is it to add extra click arguments to Totally agree that whatever we do we should make it easier to actually add those extra click arguments though e.g. through sort of |
Until we natively provide a way for people to inject / override catalog entries, we're going to see people doing the same thing |
Adding a data point of use of
I think this is a pretty advanced use case, but I think you will find it interesting @AntonyMilneQB |
AFIAK this topic comes out of #1423 as there is a subtle difference between running kedro as a package VS running kedro via KedroSession, the CLI entry point is one of the differences. I am closer to @datajoely on this, I don't think we offer a better way to achieve this.
How would removing the |
Another vote for |
Just some rough notes for now; details to be added when I get a chance...
run
?My ultimate hope here is that we can remove the project cli.py and implement something like #1041, while making #1423 much easier.
The text was updated successfully, but these errors were encountered: