Way of calling analysis process can cause import errors in third party libraries used therein

[foosel]

Problem

As mentioned in #2095 (comment), there exists an import problem when libyaml is installed on the system and hence the yaml dependency utilizes its native extension, which imports platform. Since by calling gcodeInterpreter.py the python lookup path is modified to include the directory this file resides in, platform no longer resolves to the global platform module but instead octoprint.util.platform.

This of course causes huge issues.

Solution

Change call of GCODE analysis tool to not cause issues with the python lookup path. Turning it into its own subcommand of the octoprint executable and then launching that via python -m octoprint appears to work just fine.

Implemented in c84e199

[foosel]

1.3.5 was released yesterday.