django-rest-framework/setup.cfg

[metadata]
license_file = LICENSE.md

[tool:pytest]
addopts=--tb=short --strict-markers -ra

[flake8]
ignore = E501,W504
banned-modules = json = use from rest_framework.utils import json!

[isort]
skip=.tox
atomic=true
multi_line_output=5
extra_standard_library=types
known_third_party=pytest,_pytest,django,pytz,uritemplate
known_first_party=rest_framework,tests

[coverage:run]
# NOTE: source is ignored with pytest-cov (but uses the same).
source = .
include = rest_framework/*,tests/*
branch = 1

[coverage:report]
include = rest_framework/*,tests/*
exclude_lines =
    pragma: no cover
    raise NotImplementedError
Add LICENSE.md to the built wheel (#4270) The wheel released on Pypi does not include the license file . The way to do this is by updating the setup.cfg accordingly 2016-07-18 18:08:44 +03:00			`[metadata]`
			`license_file = LICENSE.md`
Move flake8 config to setup.cfg This allows for flake8 to pick it up when running it by itself. 2017-05-16 13:18:33 +03:00
Use [tool:pytest] header in setup.cfg (#6045) 2018-06-23 01:14:26 +03:00			`[tool:pytest]`
Fix pytest warnings (#7928) * Use `--strict-markers` instead of `--strict`, as per this warning: ``` /.../_pytest/config/__init__.py:1183: PytestDeprecationWarning: The --strict option is deprecated, use --strict-markers instead. ``` * Remove config option 'testspath' - pytest is logging a warning about this being unknown: ``` /.../_pytest/config/__init__.py:1233: PytestConfigWarning: Unknown config option: testspath ``` I can't find any reference to it in the pytest docs or changelog. 2021-04-16 19:47:21 +03:00			`addopts=--tb=short --strict-markers -ra`
Move pytest config to setup.cfg (#5979) Also adds `testspath` to improve test collection performance. 2018-05-08 15:28:16 +03:00
Move flake8 config to setup.cfg This allows for flake8 to pick it up when running it by itself. 2017-05-16 13:18:33 +03:00			`[flake8]`
Update linter requirements (#7010) 2019-10-22 21:18:51 +03:00			`ignore = E501,W504`
Add banned imports to prevent standard json import 2017-07-11 00:22:55 +03:00			`banned-modules = json = use from rest_framework.utils import json!`
Upgrade isort (#5817) * Fix isort * runtests: add --diff to ISORT_ARGS * requirements-codestyle: bump isort to 4.3.3 * isort: move config to setup.cfg 2018-02-14 23:12:14 +03:00
			`[isort]`
			`skip=.tox`
			`atomic=true`
			`multi_line_output=5`
isort v5 (#7484) 2020-08-17 23:26:56 +03:00			`extra_standard_library=types`
Fixup isort command/config (#6639) 2019-05-02 03:42:10 +03:00			`known_third_party=pytest,_pytest,django,pytz,uritemplate`
			`known_first_party=rest_framework,tests`
Include coverage for tests (#5970) It is useful to see if tests itself are covered after all - missing coverage there typically indicates dead/missed code paths. This also uses `source=.` and includes (with run and report), to help Codecov with reporting. Ref: https://github.com/encode/django-rest-framework/pull/5956 2018-05-08 16:02:45 +03:00
			`[coverage:run]`
			`# NOTE: source is ignored with pytest-cov (but uses the same).`
			`source = .`
			`include = rest_framework/,tests/`
			`branch = 1`
Add NotImplementedError to coverage exclusion (#6057) 2018-06-25 00:56:31 +03:00
Include coverage for tests (#5970) It is useful to see if tests itself are covered after all - missing coverage there typically indicates dead/missed code paths. This also uses `source=.` and includes (with run and report), to help Codecov with reporting. Ref: https://github.com/encode/django-rest-framework/pull/5956 2018-05-08 16:02:45 +03:00			`[coverage:report]`
			`include = rest_framework/,tests/`
Add NotImplementedError to coverage exclusion (#6057) 2018-06-25 00:56:31 +03:00			`exclude_lines =`
			`pragma: no cover`
			`raise NotImplementedError`