zephyr/scripts/requirements.txt

Pillow
PyYAML>=5.1
breathe>=4.9.1
colorama
docutils>=0.14
gcovr
git-spindle>=2.0
gitlint
intelhex
junit2html
packaging
ply>=3.10
pyelftools>=0.24
pykwalify
pyocd>=0.21.0
pyserial
pytest
sphinx>=1.7.5
sphinx_rtd_theme
sphinx-tabs
sphinxcontrib-svg2pdfconverter
west>=0.6.2
wheel>=0.30.0
# "win32" is used for 64-bit Windows as well
windows-curses; sys_platform == "win32"
requirements: sort alphabetically Sort packages alphabetically. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-08-23 05:19:34 +08:00			`Pillow`
scripts/requirements: update PyYAML to >=5.1 sanitycheck now requires yaml.FullLoader to support generating hardware maps. This feature was introduced in PyYAML 5.1. Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no> 2019-10-29 23:43:28 +08:00			`PyYAML>=5.1`
scripts: use compatible release specifiers in requirements.txt Using exact versions for our PyPI dependencies (i.e. requirements.txt lines that look like "dependency==X.Y.Z") is rude since we're asking users to install these dependencies outside of any virtual environment. This causes conflicts with other packages which may depend on the same things as us. Use inclusive ordered comparison (>=) release specifiers instead: https://www.python.org/dev/peps/pep-0440/#inclusive-ordered-comparison If this causes problems for individual packages, we can refine them using compatible release specifiers (~=): https://www.python.org/dev/peps/pep-0440/#compatible-release Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> 2019-10-23 07:14:11 +08:00			`breathe>=4.9.1`
requirements: sort alphabetically Sort packages alphabetically. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-08-23 05:19:34 +08:00			`colorama`
scripts: use compatible release specifiers in requirements.txt Using exact versions for our PyPI dependencies (i.e. requirements.txt lines that look like "dependency==X.Y.Z") is rude since we're asking users to install these dependencies outside of any virtual environment. This causes conflicts with other packages which may depend on the same things as us. Use inclusive ordered comparison (>=) release specifiers instead: https://www.python.org/dev/peps/pep-0440/#inclusive-ordered-comparison If this causes problems for individual packages, we can refine them using compatible release specifiers (~=): https://www.python.org/dev/peps/pep-0440/#compatible-release Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> 2019-10-23 07:14:11 +08:00			`docutils>=0.14`
requirements: sort alphabetically Sort packages alphabetically. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-08-23 05:19:34 +08:00			`gcovr`
scripts: use compatible release specifiers in requirements.txt Using exact versions for our PyPI dependencies (i.e. requirements.txt lines that look like "dependency==X.Y.Z") is rude since we're asking users to install these dependencies outside of any virtual environment. This causes conflicts with other packages which may depend on the same things as us. Use inclusive ordered comparison (>=) release specifiers instead: https://www.python.org/dev/peps/pep-0440/#inclusive-ordered-comparison If this causes problems for individual packages, we can refine them using compatible release specifiers (~=): https://www.python.org/dev/peps/pep-0440/#compatible-release Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> 2019-10-23 07:14:11 +08:00			`git-spindle>=2.0`
doc: add python pip requirements.txt List all required modules in one file and just call pip with this file to install all needed modules instead of listing them individually. Added gitlint and pyocd and other required packages to the list. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-07-14 22:35:20 +08:00			`gitlint`
requirements: sort alphabetically Sort packages alphabetically. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-08-23 05:19:34 +08:00			`intelhex`
			`junit2html`
scripts: west_commands: verify minimum cmake version A recent developer experience study has pointed out that it's very common for people to miss that the minimum cmake version required by zephyr is higher than that which is commonly packaged by Linux distributions. Since this is a serious usability issue, it's worth adding extra checking from zcmake.py to make sure that west commands which run cmake always print a sensible error message if the cmake version used is too old. Make that happen. Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no> 2019-08-26 02:53:24 +08:00			`packaging`
scripts: use compatible release specifiers in requirements.txt Using exact versions for our PyPI dependencies (i.e. requirements.txt lines that look like "dependency==X.Y.Z") is rude since we're asking users to install these dependencies outside of any virtual environment. This causes conflicts with other packages which may depend on the same things as us. Use inclusive ordered comparison (>=) release specifiers instead: https://www.python.org/dev/peps/pep-0440/#inclusive-ordered-comparison If this causes problems for individual packages, we can refine them using compatible release specifiers (~=): https://www.python.org/dev/peps/pep-0440/#compatible-release Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> 2019-10-23 07:14:11 +08:00			`ply>=3.10`
			`pyelftools>=0.24`
requirements: sort alphabetically Sort packages alphabetically. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-08-23 05:19:34 +08:00			`pykwalify`
scripts: use compatible release specifiers in requirements.txt Using exact versions for our PyPI dependencies (i.e. requirements.txt lines that look like "dependency==X.Y.Z") is rude since we're asking users to install these dependencies outside of any virtual environment. This causes conflicts with other packages which may depend on the same things as us. Use inclusive ordered comparison (>=) release specifiers instead: https://www.python.org/dev/peps/pep-0440/#inclusive-ordered-comparison If this causes problems for individual packages, we can refine them using compatible release specifiers (~=): https://www.python.org/dev/peps/pep-0440/#compatible-release Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> 2019-10-23 07:14:11 +08:00			`pyocd>=0.21.0`
sanitycheck: we need pyserial for sanitycheck Needed for testing on real hardware and connecting to the serial console to capture output. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2018-05-07 22:40:51 +08:00			`pyserial`
requirements: sort alphabetically Sort packages alphabetically. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-08-23 05:19:34 +08:00			`pytest`
scripts: use compatible release specifiers in requirements.txt Using exact versions for our PyPI dependencies (i.e. requirements.txt lines that look like "dependency==X.Y.Z") is rude since we're asking users to install these dependencies outside of any virtual environment. This causes conflicts with other packages which may depend on the same things as us. Use inclusive ordered comparison (>=) release specifiers instead: https://www.python.org/dev/peps/pep-0440/#inclusive-ordered-comparison If this causes problems for individual packages, we can refine them using compatible release specifiers (~=): https://www.python.org/dev/peps/pep-0440/#compatible-release Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> 2019-10-23 07:14:11 +08:00			`sphinx>=1.7.5`
requirements: sort alphabetically Sort packages alphabetically. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-08-23 05:19:34 +08:00			`sphinx_rtd_theme`
doc: add sphinx-tabs extension The sphinx-tabs extension provides a tabbed interface within documents that will let us dynamically display information based on a user selection, for example, for instruction variations based on the user's development OS (Linux, macOS, Windows). I'm adding this early so it can get integrated into the CI doc build before subsequent PRs using this extension are submitted. Signed-off-by: David B. Kinder <david.b.kinder@intel.com> 2019-08-24 03:40:08 +08:00			`sphinx-tabs`
requirements: sort alphabetically Sort packages alphabetically. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-08-23 05:19:34 +08:00			`sphinxcontrib-svg2pdfconverter`
west: update requirements.txt to avoid west 0.6.1 Update scripts/requirements.txt to use 0.6.2 or later (avoiding 0.6.1 that has an known issue) Signed-off-by: David B. Kinder <david.b.kinder@intel.com> 2019-09-07 00:00:08 +08:00			`west>=0.6.2`
scripts: use compatible release specifiers in requirements.txt Using exact versions for our PyPI dependencies (i.e. requirements.txt lines that look like "dependency==X.Y.Z") is rude since we're asking users to install these dependencies outside of any virtual environment. This causes conflicts with other packages which may depend on the same things as us. Use inclusive ordered comparison (>=) release specifiers instead: https://www.python.org/dev/peps/pep-0440/#inclusive-ordered-comparison If this causes problems for individual packages, we can refine them using compatible release specifiers (~=): https://www.python.org/dev/peps/pep-0440/#compatible-release Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> 2019-10-23 07:14:11 +08:00			`wheel>=0.30.0`
scripts: install windows-curses package on Windows The new menuconfig implementation needs it when run on Windows. Use an environment marker to only install windows-curses on Windows. See https://www.python.org/dev/peps/pep-0508/#id23. From some googling, sys_platform might be more widely supported than platform_system, so use that. Suggested-by: Sebastian Bøe <sebastian.boe@nordicsemi.no> Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com> 2018-05-07 19:27:49 +08:00			`# "win32" is used for 64-bit Windows as well`
			`windows-curses; sys_platform == "win32"`