No, the original code is in python 3. First machine is 0.15.1 and the second machine which used conda is 0.15.0. I didn't manually make change in configuration.
AntsySeagull45 kudos on sorting it out 🙂
quick note, trains-agent will try to run the python version specified by the original Task. i.e. if you were running python3.7 it will first try to look for python 3.7 then if it is not there it will run the default python3. This allows a system with multiple python versions to run exactly the python version you had on your original machine. The fact that it was trying to run python2 is quite odd, one explanation I can think of is if the original experiment was run on python2.7...
The other explanation is it default to the python version that runs the trains-agent! So if you managed to run the trains-agent with python2 this will be the version it will default to.
You can always verify the default python version, when running the trains-agent, it print the configuration, and you should see something like:agent.default_python = 3.6
Hi AntsySeagull45
Any chance the original code was running with python2?
Which version of trains-agent are you using?
One more question, in the second log, trains agent is configured with Conda, on the first it is configured with pip, or at least this is what it looks like, can you confirm?
Not sure why it defaulted to python2 in base env. Thanks
fixed now, trains-agent was running in conda base environment in the problematic machine. Created a new environment and ran it inside that and the code is working.