This PR simplifies and eliminates conflict between the ESP32 IDF python installation and the one Sming uses.
esp32 IDF uses its own virtual python environment and that location gets added to the system path.
That means if our PYTHON variable doesn't contain an absolute path (e.g. python3, the default) then for esp32 builds only it ends up using the IDF python instead. Which is problematic.
So, do we really need all that crud on the path?
Turns out we don't. This PR gets rid of stuff which isn't necessary.
NB. Checked current IDF behaviour and their export script still puts everything in the PATH.
A further simplification is removal of core python requirements from the main Python environment. These aren't required.
This PR simplifies and eliminates conflict between the ESP32 IDF python installation and the one Sming uses.
esp32 IDF uses its own virtual python environment and that location gets added to the system path. That means if our
PYTHONvariable doesn't contain an absolute path (e.g.python3, the default) then for esp32 builds only it ends up using the IDF python instead. Which is problematic.So, do we really need all that crud on the path? Turns out we don't. This PR gets rid of stuff which isn't necessary.
NB. Checked current IDF behaviour and their export script still puts everything in the PATH.
A further simplification is removal of core python requirements from the main Python environment. These aren't required.