setup.cfg

[tool:pytest]
norecursedirs=node_modules bower_components
xfail_strict=true

[tool:isort]
profile = black
multi_line_output = 3


[tool:flake8]
exclude = venv*,__pycache__,node_modules,cache,build
max-line-length = 120
extend_ignore=B306, W504, E203
bump test requirements to most recent 2016-09-09 16:29:30 +01:00			`[tool:pytest]`
define isort first party (app and tests) we were seeing isort produce different outputs locally and in docker - this was due to it having different opinions about whether the tests module (ie all our unit tests) is a first party (local) or third party (pip installed) import. It's a first party import, so by defining this in the setup.cfg isort settings, we can force it to be consistent between environments. Note: I don't know why it was different in the first place though 2018-04-25 14:12:58 +01:00			`norecursedirs=node_modules bower_components`
make xfail passes (unexpected passes) fail test runs 2017-02-23 16:36:16 +00:00			`xfail_strict=true`
Enforce order and style of imports Done using isort[1], with the following command: ``` isort -rc ./app ./tests ``` Adds linting to the `run_tests.sh` script to stop badly-sorted imports getting re-introduced. Chosen style is ‘Vertical Hanging Indent’ with trailing commas, because I think it gives the cleanest diffs, eg: ``` from third_party import ( lib1, lib2, lib3, lib4, ) ``` 1. https://pypi.python.org/pypi/isort 2018-02-20 11:22:17 +00:00
merge from main 2023-08-25 08:57:24 -07:00			`[tool:isort]`
			`profile = black`
			`multi_line_output = 3`


			`[tool:flake8]`
			`exclude = venv*,__pycache__,node_modules,cache,build`
			`max-line-length = 120`
			`extend_ignore=B306, W504, E203`