OVMS3-idf/requirements.txt

# This is a list of python packages needed for ESP-IDF. This file is used with pip.
# Please see the Get Started section of the ESP-IDF Programming Guide for further information.
#
setuptools
# The setuptools package is required to install source distributions and on some systems is not installed by default.
# Please keep it as the first item of this list.
#
click>=5.0
pyserial>=3.0
future>=0.15.2
cryptography>=2.1.4
pyparsing>=2.0.3,<2.4.0
pyelftools>=0.22
# windows-curses are required in Windows command line but cannot be installed in MSYS2. A requirement like
# "windows-curses; sys_platform == 'win32'" would want to install the package on both of them. There is no environment
# marker for detecting MSYS2. So instead, a dummy custom package is used with "windows-curses" dependency for Windows
# command line.
file://${IDF_PATH}/tools/kconfig_new/esp-windows-curses; sys_platform == 'win32'
docs: make the use of pip install clear 2018-08-23 09:16:56 +00:00			`# This is a list of python packages needed for ESP-IDF. This file is used with pip.`
			`# Please see the Get Started section of the ESP-IDF Programming Guide for further information.`
Add python-future by using python requirements file 2018-08-15 07:52:07 +00:00			`#`
Add required Python packages On some systems pip and setuptools are no longer installed as dependencies of the python packages. This commit adds the requirement for these packages. 2018-09-07 06:44:19 +00:00			`setuptools`
			`# The setuptools package is required to install source distributions and on some systems is not installed by default.`
			`# Please keep it as the first item of this list.`
			`#`
idf.py: Add support for action specific options Changes argument parsing mechanism from argparse to a new one, that provides better support for extensions and options that are only applicable to specific subcommands, Breaking changes: 1. All global options should go before subcommands, i.e. `idf.py build -C ~/some/project` will not work anymore, only `idf.py -C ~/some/project build` is acceptable 2. To provide multiple values to an option like `--define-cache-entry` it's necessary to repeat option many times, i.e. `idf.py -D entry1 entry2 entry3` will not work, right way is: `idf.py -D entry1 -D entry2 -D entry3` At the moment there are 3 options like this: `--define-cache-entry` in base list and `--test-components` and `--test-exclude-components` in the unit test extensions 3. Drops `defconfig` and `bootloader-clean` subcommands Closes https://github.com/espressif/esp-idf/issues/3570 Closes https://github.com/espressif/esp-idf/issues/3571 2019-04-10 16:06:52 +00:00			`click>=5.0`
Add python-future by using python requirements file 2018-08-15 07:52:07 +00:00			`pyserial>=3.0`
Change python-future to 0.15.2 (again) Merges https://github.com/espressif/esp-idf/pull/2492 2018-09-29 10:00:12 +00:00			`future>=0.15.2`
Update minimum version for cryptography package required 2018-11-16 05:57:00 +00:00			`cryptography>=2.1.4`
Temporarily fix incompatibility with pyparsing 2.4.0 2019-04-17 07:57:42 +00:00			`pyparsing>=2.0.3,<2.4.0`
sys_view: Adds processing scripts for heap & log traces 2018-12-12 17:38:23 +00:00			`pyelftools>=0.22`
Update kconfiglib to upstream version and replace mconf-idf Special thanks to @ulfalizer for the helpful suggestions regarding kconfiglib. "rsource" option is available for relative path includes Closes https://github.com/espressif/esp-idf/issues/4064 2019-09-10 07:58:52 +00:00			`# windows-curses are required in Windows command line but cannot be installed in MSYS2. A requirement like`
			`# "windows-curses; sys_platform == 'win32'" would want to install the package on both of them. There is no environment`
			`# marker for detecting MSYS2. So instead, a dummy custom package is used with "windows-curses" dependency for Windows`
			`# command line.`
			`file://${IDF_PATH}/tools/kconfig_new/esp-windows-curses; sys_platform == 'win32'`