Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hey Everyone! First Post Here. My Issue Is The Python_Binary I Set In The .Conf File Doesn'T Seem To Get Used By The Task I'M Running. The Task'S Output Confirms

Hey everyone! First post here. My issue is the python_binary I set in the .conf file doesn't seem to get used by the task I'm running. The task's output confirms
agent.python_binary = 3.11
but then shows
agent.default_python = 3.9
and even more puzzlingly then prints

Python executable with version '3.10' requested by the Task, not found in path, using '/opt/conda/envs/myenv/bin/python3' (v3.9.18) instead

So my main question is, how come clearml doesn't just enforce that the env use the "python_binary" (3.11), or create a new env with one? I thought that was its purpose.

Second, where is "default_python" (3.9) coming from? Is that whatever was used when the task was first run?

Third, why would there be yet a third python version (3.10) being requested by the task?

Sorry if the answers are out there already, I'm having a hard time finding them.

  
  
Posted 7 months ago
Votes Newest

Answers 5


as a followup on this one @<1523701070390366208:profile|CostlyOstrich36> .
how do I make my agent install python 3.9 and not 3.7?

agent.default_python: 3.9
agent.python_binary: 3.9

but getting in the task:

Python executable with version '3.9' requested by the Task, not found in path, using '/clearml_agent_venv/bin/python3' (v3.7.3) instead
  
  
Posted 7 months ago

Is there any specific reason you're not running in docker mode? Running in docker would simplify things

  
  
Posted 7 months ago

The setting for the python binary should be explicit since the agent can't really 'detect' where you installed your python
For example:
agent.python_binary: "C:\ProgramData\Anaconda3\python.exe"

  
  
Posted 7 months ago

Hi @<1618780810947596288:profile|ExuberantLion50> , what happens if you set the python binary path itself? Also, any specific reason you're not running in docker mode?

  
  
Posted 7 months ago

@<1523701070390366208:profile|CostlyOstrich36> I will try using a full path. hmm, any reason i'm not running in docker mode.... I suppose because I'm new to the platform and don't know how yet? Do you recommend that I make the switch?

  
  
Posted 7 months ago