Hmm, we could add an optional test for the python version, and the fail the Task if the python version is not found. wdyt?

Won't it be too harsh to have system wide restriction like that ?

I would prefer controlled behavior than some available version being used. Here triggered a bunch of jobs that all went fine and even evaluations were fine and then when we triggered a inference deploy it failed

then when we triggered a inference deploy it failed

How would you control it? Is it based on a Task ? like a property "match python version" ?

that or in clearml.conf or both

Hmm, interesting, why would you want that? Is this because some of the packages will fail?

In this case, particularly because of pickle protocol version between 3.7 and 3.8