The tag does exist though

Can you do the top URL for starters and then clone_to_dir to the directory in question?

No sorry

I was trying to say all of those commands are exposed via the kedro starters cli

So you can provide the arguments of repo, folder, tag

Oh, sorry gotcha. This command worked:

kedro new -s https://github.com/kedro-org/kedro-starters/ --checkout 0.18.0 --directory standalone-datacatalog

Would you mind raising a issue on kedro starters?

Sure, I will just check the guidelines for raising issues before = ).

If you create an issue there are templates that take you through it ☺️

Will do that then!

Done, thanks for the help.

I installed latest kedro version today on Windows 11 in a new conda env using python 3.7, all according to the provided tutorial, and kedro-info is running fine. But when trying to run hello world.py it is throwing an error - 'kedro.io' module is not available | 'kedro' is not a package. Anybody facing the same issue.....

Hello, I needed some help understanding dataset versioning. Specifically, I keep running into errors where the save path must not exist if versioning is enabled? Should I disable versioning if I’m doing some testing in ipython?

Which tutorial are you running? What does kedro -V gives you?

It's likely you have an existing file with the exact same name.

Is there a parameter for the catalog that would handle this?

For example, say your file is called data.csv If you turn on versioning, it will be data.csv/timestamp/data.csv instead

Also where is it fetching the time stamp from?

The timestamp will be a default timestamp, each time you run kedro pipeline it generates a timestamp

You just need to remove the existing data.cvs which cause name collision

So if I make no change to my code, the node I run will have a name collision with versioning on. But if I change the code, the version time stamp changes?

Not sure if I am following, what code change are you referring?

Ok…let me back up. So I have a node that I’ve made some changes to. I save those and have versioning on. When I run the node the first time it runs fine. But if I make no change and rerun it, I get the error.

Perhaps node is incorrect as well. I have a segment of the pipeline I’m running using to_nodes

So this is probably because when you run the pipeline first time, you have no version on. It generates a file called path/filename

That’s true I didn’t. I enabled it after the fact

And now u turn on versioning, it tries to generate a path called path/filename/timestamp/filename, but the existing file collide with the existing file

The filesystem does not allow the same name being reused