Thanks Martin.
I'll use this hack next time, but I think it might cause runtime issues when we use it naive way.
a different use for task_name will be more intuitive (especially when get_task works like this)

IrritableJellyfish76 point taken, suggestions on improving the interface ?

IrritableJellyfish76 hmm maybe we should an an extra argument partial_name_matching=False to maintain backwards compatibility?

AgitatedDove14 As a user I excepted that task_name will be a str, so from my point of view, it should be explicit as same as in get_task.
one option is to validate task_name not contains any regex related chars in init phase, second option is to add explicit task_name option to the interface and not all-in-one option.

Hi IrritableJellyfish76
https://clear.ml/docs/latest/docs/references/sdk/task#taskget_tasks

task_name

(

str

) – The full name or partial name of the Tasks to match within the specified

project_name

(or all projects if

project_name

is

None

). This method supports regular expressions for name matching. (Optional)

You are right, this is a bit confusing, I will make sure that we add in the docstring an example of exact match. For future reference, in order to get exactly the name " exact_task_name_here " , you should pass "^exact_task_name_here$"