django-rest-framework/setup.cfg

[metadata]
license_files = LICENSE.md

[tool:pytest]
addopts=--tb=short --strict-markers -ra
testpaths = tests
filterwarnings = ignore:CoreAPI compatibility is deprecated*:rest_framework.RemovedInDRF317Warning

[flake8]
ignore = E501,W503,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

[codespell]
# Ref: https://github.com/codespell-project/codespell#using-a-config-file
skip = */kickstarter-announcement.md,*.js,*.map,*.po
ignore-words-list = fo,malcom,ser
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]`
Fix setuptools warning about license_files (#8595) 2022-08-10 15:47:39 +03:00			`license_files = 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`
Fix typo in setup.cfg setting 2024-04-26 19:02:19 +03:00			`testpaths = tests`
Added Deprecation Warnings for CoreAPI (#7519) * Added Deprecation Warnings for CoreAPI * Bumped removal to DRF315 * Update rest_framework/__init__.py * Update rest_framework/filters.py * Update rest_framework/filters.py * Update tests/schemas/test_coreapi.py * Update rest_framework/filters.py * Update rest_framework/filters.py * Update tests/schemas/test_coreapi.py * Update tests/schemas/test_coreapi.py * Update tests/schemas/test_coreapi.py * Update tests/schemas/test_coreapi.py * Update rest_framework/pagination.py * Update rest_framework/pagination.py * Update rest_framework/pagination.py * Update rest_framework/pagination.py * Update rest_framework/schemas/coreapi.py * Update rest_framework/schemas/coreapi.py * Update rest_framework/schemas/coreapi.py * Update rest_framework/schemas/coreapi.py * Update rest_framework/schemas/coreapi.py * Update tests/schemas/test_coreapi.py * Update setup.cfg * Update tests/schemas/test_coreapi.py * Update tests/schemas/test_coreapi.py * Update tests/schemas/test_coreapi.py * Update tests/schemas/test_coreapi.py * Update tests/schemas/test_coreapi.py * Update tests/schemas/test_coreapi.py * Update rest_framework/pagination.py --------- Co-authored-by: Asif Saif Uddin <auvipy@gmail.com> 2023-06-13 09:55:22 +03:00			`filterwarnings = ignore:CoreAPI compatibility is deprecated*:rest_framework.RemovedInDRF317Warning`
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]`
Change semantic of OR of two permission classes (#7522) * Change semantic of OR of two permission classes The original semantic of OR is defined as: the request pass either of the two has_permission() check, and pass either of the two has_object_permission() check, which could lead to situations that a request passes has_permission() but fails on has_object_permission() of Permission Class A, fails has_permission() but passes has_object_permission() of Permission Class B, passes the OR permission check. This should not be the desired permission check semantic in applications, because such a request should fail on either Permission Class (on Django object permission) alone, but passes the OR or the two. My code fix this by changing the semantic so that the request has to pass either class's has_permission() and has_object_permission() to get the Django object permission of the OR check. * Update rest_framework/permissions.py * Update setup.cfg Co-authored-by: Mark Yu <markyu98@outlook.com> Co-authored-by: Tom Christie <tom@tomchristie.com> 2022-09-21 14:19:33 +03:00			`ignore = E501,W503,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`
Add codespell: config + workflow to detect new typos. Get some typos fixed (#9234) * Do not ignore .codespellrc from git * Add rudimentary codespell config * Add pre-commit definition for codespell * more custom skips for codespell - long lines, lines with ú etc * [DATALAD RUNCMD] Do interactive fixing of some ambigous typos === Do not change lines below === { "chain": [], "cmd": "codespell -w -i 3 -C 2 ./docs/community/release-notes.md", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ * BF: pre-commit needs to duplicate some of the skips for codespell Known issue -- yet to be addressed: https://github.com/codespell-project/codespell/issues/3196 * Move codespell configuration into setup.cfg 2024-02-28 14:01:49 +03:00
			`[codespell]`
			`# Ref: https://github.com/codespell-project/codespell#using-a-config-file`
			`skip = /kickstarter-announcement.md,.js,.map,.po`
			`ignore-words-list = fo,malcom,ser`