Windows MSYS2: ESP-IDF v3.2-dev requires newer Python package future-0.16.0

[papaluna]

v3.2-dev is checking the Python requirements during each build and that is a good thing.

The build stops during the process of checking the Python requirements when using the Windows toolchain with ESP-IDF v3.2-dev (latest). It reports that a newer version of the Python package "future" is required.

So I have followed the instructions in the log to upgrade it (

Code: Select all

C:/msys32/mingw32/bin/python.exe -m pip install -r C:/myiot/esp/esp-idf/requirements.txt

) and that works fine.

=> Is it possible to include this newer version of Python package "future" in the MSYS2 bundle that is documented at https://docs.espressif.com/projects/esp ... setup.html so the build proceeds correctly from the first time without installing/upgrading Pyhon packages manually? This is one barrier less for new ESP-IDF Windows developers.

Code: Select all

### Install specific PIP package version for ESP-IDF
C:/msys32/mingw32/bin/python.exe -m pip install -r C:/myiot/esp/esp-idf/requirements.txt
	#OUTPUT#:
		Requirement already satisfied: pyserial>=3.0 in c:/msys32/mingw32/lib/python2.7/site-packages (from -r C:/myiot/esp/esp-idf/requirements.txt (line 4))
		Collecting future>=0.16.0 (from -r C:/myiot/esp/esp-idf/requirements.txt (line 5))
		  Downloading https://files.pythonhosted.org/packages/00/2b/8d082ddfed935f3608cc61140df6dcbf0edea1bc3ab52fb6c29ae3e81e85/future-0.16.0.tar.gz (824kB)
		    100% |################################| 829kB 1.1MB/s
		Installing collected packages: future
		  Running setup.py install for future ... done
		Successfully installed future-0.16.0

[ESP_Angus]

Hi Paul,

A very reasonable request, and thanks for reminding us about it! Will add.


Angus