On macOS High Sierra (10.13.6) Python 2.7 is shipped by Apple, which lives in /usr/bin/python.
I've also installed Python 3.7, which lives in "/Library/Frameworks/Python.framework/Versions/3.7/bin/python3".
Path is also set via .bash_profile so I can call python3 directly.
I want to use my Python3.7 installation for running any Robotframework scripts via Sublime.
I use Sublime 3.1.1, Robotframework 3.0.4 with Robotframework-seleniumlibrary 3.1.1.
I specified the "path_to_python" section in user config, but this didn't changed anything.
Build in ST always calls the python, not the python3 command.
I've looked in the Robot.sublime-build file located in sublime-robot-framework-assistant package folder. I changed the cmd argument to python3 and this works for now. But if there is an update of your really cool plugin my changes will be overwritten, right?
Is there any chance to specify not only the path to python binary, but also which command is used?
On macOS High Sierra (10.13.6) Python 2.7 is shipped by Apple, which lives in /usr/bin/python. I've also installed Python 3.7, which lives in "/Library/Frameworks/Python.framework/Versions/3.7/bin/python3". Path is also set via .bash_profile so I can call python3 directly.
I want to use my Python3.7 installation for running any Robotframework scripts via Sublime. I use Sublime 3.1.1, Robotframework 3.0.4 with Robotframework-seleniumlibrary 3.1.1.
I specified the "path_to_python" section in user config, but this didn't changed anything. Build in ST always calls the python, not the python3 command.
I've looked in the Robot.sublime-build file located in sublime-robot-framework-assistant package folder. I changed the cmd argument to python3 and this works for now. But if there is an update of your really cool plugin my changes will be overwritten, right?
Is there any chance to specify not only the path to python binary, but also which command is used?