Now it's okey. I have found a more intuitive way to get around. I was facing the classic 'xy' problem :)

But you can get that directly, Task.get_task(...).artifacts[name].url , no? Am I missing something?

My idea is to take advantage of the capability of getting parameters connected to a task from another task to read the path where the artifacts are stored locally, so I don't have to define it again in each script corresponding to a different task.

I guess that was never the intention of the function, it just returns the internal representation. Actually my question would be, how do you use it, and why? :)

Sure, but I mean, apart from label it as a local path, what's the point of renaming the original path if my goal is to access it later using the name I gave it?

But I'm sure there is a cleaner way to proceed.

Maybe ?!
path = task.get_output_destination().replace('file://', '', 1)

I currently deal with that by skipping the first 5 characters of the path, i. e. the 'file:' part. But I'm sure there is a cleaner way to proceed.

No, file://home/user/local_storage_path doesn't exist.

you mean "/home/user/local_storage_path" does not exist ?

But this path actually does not exist in my system, so how should I fix that?

Hi GiganticTurtle0
you should actually get " file://home/user/local_storage_path "
With "file://" prefix.
We always store the file:// prefix to note that this is a local path