p53209761
/
test_ok2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
test_ok2/setup.cfg

106 lines
2.5 KiB
INI
Raw Normal View History

modernize packaging for setuptools>30.3
2018-10-15 03:44:32 +08:00
[metadata]
name = pytest
description = pytest: simple powerful testing with Python
long_description = file: README.rst
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
long_description_content_type = text/x-rst
fix url quotes in setup.cfg metadata
2018-10-17 03:48:39 +08:00
url = https://docs.pytest.org/en/latest/
move most setuptools parameters over to setup.cfg
2018-10-15 13:30:07 +08:00
author = Holger Krekel, Bruno Oliveira, Ronny Pfannschmidt, Floris Bruynooghe, Brianna Laugher, Florian Bruhin and others
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
license = MIT
[pre-commit.ci] pre-commit autoupdate (#11084) updates: - [github.com/asottile/setup-cfg-fmt: v2.2.0 → v2.3.0](https://github.com/asottile/setup-cfg-fmt/compare/v2.2.0...v2.3.0)
2023-06-06 17:13:38 +08:00
license_files = LICENSE
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
platforms = unix, linux, osx, cygwin, win32
modernize packaging for setuptools>30.3
2018-10-15 03:44:32 +08:00
classifiers =
Development Status :: 6 - Mature
Intended Audience :: Developers
License :: OSI Approved :: MIT License
Operating System :: MacOS :: MacOS X
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
Operating System :: Microsoft :: Windows
Operating System :: POSIX
Programming Language :: Python :: 3
Drop Python 2.7 and 3.4 support * Update setup.py requires and classifiers * Drop Python 2.7 and 3.4 from CI * Update docs dropping 2.7 and 3.4 support * Fix mock imports and remove tests related to pypi's mock module * Add py27 and 34 support docs to the sidebar * Remove usage of six from tmpdir * Remove six.PY* code blocks * Remove sys.version_info related code * Cleanup compat * Remove obsolete safe_str * Remove obsolete __unicode__ methods * Remove compat.PY35 and compat.PY36: not really needed anymore * Remove unused UNICODE_TYPES * Remove Jython specific code * Remove some Python 2 references from docs Related to #5275
2019-05-28 07:31:52 +08:00
Programming Language :: Python :: 3 :: Only
Programming Language :: Python :: 3.8
Fix tests for python3.9
2020-05-07 20:26:55 +08:00
Programming Language :: Python :: 3.9
Add classifier for Python 3.10 and CHANGELOG entry
2021-03-27 22:04:26 +08:00
Programming Language :: Python :: 3.10
Add the PyPI classifier for Python 3.11 (#10426)
2022-10-26 00:43:59 +08:00
Programming Language :: Python :: 3.11
Declare support for Python 3.12
2023-05-23 20:13:55 +08:00
Programming Language :: Python :: 3.12
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
Topic :: Software Development :: Libraries
Topic :: Software Development :: Testing
Topic :: Utilities
keywords = test, unittest
project_urls =
Add Changelog to setup.cfg (#8166) Co-authored-by: Thomas Grainger <tagrain@gmail.com> Co-authored-by: Bruno Oliveira <nicoddemus@gmail.com>
2020-12-18 00:55:36 +08:00
Changelog=https://docs.pytest.org/en/stable/changelog.html
Twitter=https://twitter.com/pytestdotorg
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
Source=https://github.com/pytest-dev/pytest
Tracker=https://github.com/pytest-dev/pytest/issues
move most setuptools parameters over to setup.cfg
2018-10-15 13:30:07 +08:00
[options]
packages =
_pytest
_pytest._code
Fix usages of py.io.saferepr
2019-01-21 02:45:12 +08:00
_pytest._io
vendor py.path and py.error
2022-10-19 22:10:49 +08:00
_pytest._py
Fix usages of py.io.saferepr
2019-01-21 02:45:12 +08:00
_pytest.assertion
move most setuptools parameters over to setup.cfg
2018-10-15 13:30:07 +08:00
_pytest.config
Fix usages of py.io.saferepr
2019-01-21 02:45:12 +08:00
_pytest.mark
Convert pytest.py into a package As discussed in https://github.com/pytest-dev/pytest/issues/3342, this is the first step to make pytest support static typing fully
2019-12-03 02:18:04 +08:00
pytest
vendor py.path and py.error
2022-10-19 22:10:49 +08:00
py_modules = py
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
install_requires =
iniconfig
packaging
Fixes for typed pluggy Since version 1.3 pluggy added typing, which requires some fixes to please mypy.
2023-08-26 14:53:45 +08:00
pluggy>=1.3.0,<2.0
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
colorama;sys_platform=="win32"
fallback to native traceback when handling ExceptionGroup (take 2) [SQUASH] (#10209) * Squashed commit of the following: commit 41d339c46763bbe26123e1e6504b6e32290e33e1 Author: Cheukting <cheukting.ho@gmail.com> Date: Thu Jun 23 17:01:04 2022 +0800 test in all py versions commit b3572a5a12672228c3276fc8c8e05980dfb7888a Author: Cheukting <cheukting.ho@gmail.com> Date: Thu Jun 23 16:41:06 2022 +0800 add test commit 7166a2a51e4f99046b028b663c193d8b558c7fd4 Author: Cheukting <cheukting.ho@gmail.com> Date: Thu Jun 23 16:00:07 2022 +0800 update changelog commit b958c73d489157f0c0d4e46425083a5e2e2bc851 Author: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Thu Jun 23 07:50:52 2022 +0000 [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci commit ea7f376c6ca37c40c83df0e4a1cfaaedb34bae91 Author: Cheukting <cheukting.ho@gmail.com> Date: Thu Jun 23 15:48:21 2022 +0800 Fix MyPy commit 97469beb1da40257e9a061a5e19548546c9312c4 Author: Cheukting <cheukting.ho@gmail.com> Date: Thu Jun 23 15:03:48 2022 +0800 fix if ExceptionGroup not exist commit 84e553642cd69b4d499231d733df91ebfa84c7ad Author: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Thu Jun 23 03:43:27 2022 +0000 [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci commit 76bbef449b88bbd74fb5cca3b5293337a624ef03 Author: Cheukting <cheukting.ho@gmail.com> Date: Thu Jun 23 11:40:41 2022 +0800 adding changelog commit db82bebc5a4969e2083adcd97bdfd2a63bb17d98 Author: Cheukting <cheukting.ho@gmail.com> Date: Thu Jun 23 11:33:10 2022 +0800 fall back to native when handeling to exception groups * Typed ExceptionGroupTypes and changed to BaseExceptionGroup, fixed exceptionchain (excinfo->excinfo_, set reprcrash. Extended tests, though they're wip. * added exceptiongroup to pre-commit-config, moved away from tuple to directly defining BaseExceptionGroup, added block comment, added match line for inner exception, changked mark.skipif to importorskip to not need top-level import, changed tox.ini a bit - only uncovered should now be py37 without exceptiongroup, due to hypothesis * added py311-exceptiongroup to github CI, exceptiongroup is now a hard dependency on py<3.11, renamed bad variable names * added use_coverage to ubuntu-py311 * import BaseExceptionGroup with explicit version check instead of try/catch * removed from CI, added comments to tox and pre-commit
2022-08-18 00:16:32 +08:00
exceptiongroup>=1.0.0rc8;python_version<"3.11"
Use tomllib on Python 3.11 (#9741)
2022-04-18 02:11:17 +08:00
tomli>=1.0.0;python_version<"3.11"
Drop Python 3.7
2023-07-01 05:55:42 +08:00
python_requires = >=3.8
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
package_dir =
=src
setup_requires =
fixes #8133: mitigate regendoc issues wrt PRETEND_VERSION this issues is less likely to hit due to the recent regendoc release which includes a wheel * migrate to setuptools_scm 6.3.2 * use SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST
2020-12-13 18:10:06 +08:00
setuptools
setuptools-scm>=6.0
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
zip_safe = no
modernize packaging for setuptools>30.3
2018-10-15 03:44:32 +08:00
move most setuptools parameters over to setup.cfg
2018-10-15 13:30:07 +08:00
[options.entry_points]
console_scripts =
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
pytest=pytest:console_main
py.test=pytest:console_main
[options.extras_require]
testing =
argcomplete
Drop attrs dependency, use dataclasses instead (#10669) Since pytest now requires Python>=3.7, we can use the stdlib attrs clone, dataclasses, instead of the OG package. attrs is still somewhat nicer than dataclasses and has some extra functionality, but for pytest usage there's not really a justification IMO to impose the extra dependency on users when a standard alternative exists.
2023-01-20 17:13:36 +08:00
attrs>=19.2.0
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
hypothesis>=3.56
mock
nose
Make pygments part of 'testing' extras Tests in test_terminalwriter depend on pygments being installed to work, so it should be installed with the `testing` extras.
2021-04-24 21:09:11 +08:00
pygments>=2.7.2
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
requests
testing: install setuptools to fix pkg_resources import in a test Since Python 3.12, setuptools is no longer installed by default in venvs. We have a test which uses it, so add it to the testing extra.
2023-05-23 20:10:46 +08:00
setuptools
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
xmlschema
modernize packaging for setuptools>30.3
2018-10-15 03:44:32 +08:00
Publish our types
2020-07-04 17:30:40 +08:00
[options.package_data]
_pytest = py.typed
pytest = py.typed
add setup.cfg for building sphinx_docs
2013-10-03 18:35:13 +08:00
[build_sphinx]
setup.cfg: fix setuptools dash-separator warnings Warnings like this: python3.9/site-packages/setuptools/dist.py:634: UserWarning: Usage of dash-separated 'upload-dir' will not be supported in future versions. Please use the underscore name 'upload_dir' instead
2021-03-14 02:30:24 +08:00
source_dir = doc/en/
build_dir = doc/build
add setup.cfg for building sphinx_docs
2013-10-03 18:35:13 +08:00
all_files = 1
restore setuptools_scm write_to usage
2017-04-23 22:59:08 +08:00
[check-manifest]
ignore =
Run setup-py-upgrade and setup-cfg-fmt - also ran `pre-commit autoupdate` - https://github.com/asottile/setup-py-upgrade - https://github.com/asottile/setup-cfg-fmt
2020-06-05 00:58:28 +08:00
src/_pytest/_version.py
restore setuptools_scm write_to usage
2017-04-23 22:59:08 +08:00
configure a plain "devpi upload" to create sdist and universal wheel
2015-07-09 20:56:56 +08:00
[devpi:upload]
formats = sdist.tgz,bdist_wheel
Add rudimentary mypy type checking Add a very lax mypy configuration, add it to tox -e linting, and fix/ignore the few errors that come up. The idea is to get it running before diving in too much. This enables: - Progressively adding type annotations and enabling more strict options, which will improve the codebase (IMO). - Annotating the public API in-line, and eventually exposing it to library users who use type checkers (with a py.typed file). Though, none of this is done yet. Refs https://github.com/pytest-dev/pytest/issues/3342.
2019-07-08 15:04:19 +08:00
[mypy]
mypy: config: use mypy_path=src This allows for checking files inside of "testing" without having "src/…" as an argument also.
2019-11-19 01:12:13 +08:00
mypy_path = src
Enable check_untyped_defs mypy option for testing/ too
2020-05-01 19:40:17 +08:00
check_untyped_defs = True
typing: set disallow_any_generics This prevents referring to a generic type without filling in its generic type parameters. The FixtureDef typing might need some more refining in the future.
2020-08-01 18:06:13 +08:00
disallow_any_generics = True
Add rudimentary mypy type checking Add a very lax mypy configuration, add it to tox -e linting, and fix/ignore the few errors that come up. The idea is to get it running before diving in too much. This enables: - Progressively adding type annotations and enabling more strict options, which will improve the codebase (IMO). - Annotating the public API in-line, and eventually exposing it to library users who use type checkers (with a py.typed file). Though, none of this is done yet. Refs https://github.com/pytest-dev/pytest/issues/3342.
2019-07-08 15:04:19 +08:00
ignore_missing_imports = True
mypy: show_error_codes=True
2020-01-28 05:18:35 +08:00
show_error_codes = True
Add rudimentary mypy type checking Add a very lax mypy configuration, add it to tox -e linting, and fix/ignore the few errors that come up. The idea is to get it running before diving in too much. This enables: - Progressively adding type annotations and enabling more strict options, which will improve the codebase (IMO). - Annotating the public API in-line, and eventually exposing it to library users who use type checkers (with a py.typed file). Though, none of this is done yet. Refs https://github.com/pytest-dev/pytest/issues/3342.
2019-07-08 15:04:19 +08:00
strict_equality = True
warn_redundant_casts = True
warn_return_any = True
typing: set warn_unreachable This makes mypy raise an error whenever it detects code which is statically unreachable, e.g. x: int if isinstance(x, str): ... # Statement is unreachable [unreachable] This is really neat and finds quite a few logic and typing bugs. Sometimes the code is intentionally unreachable in terms of types, e.g. raising TypeError when a function is given an argument with a wrong type. In these cases a `type: ignore[unreachable]` is needed, but I think it's a nice code hint.
2020-08-04 00:15:21 +08:00
warn_unreachable = True
Add rudimentary mypy type checking Add a very lax mypy configuration, add it to tox -e linting, and fix/ignore the few errors that come up. The idea is to get it running before diving in too much. This enables: - Progressively adding type annotations and enabling more strict options, which will improve the codebase (IMO). - Annotating the public API in-line, and eventually exposing it to library users who use type checkers (with a py.typed file). Though, none of this is done yet. Refs https://github.com/pytest-dev/pytest/issues/3342.
2019-07-08 15:04:19 +08:00
warn_unused_configs = True
typing: set no_implicit_reexport In Python, if module A defines a name `name`, and module B does `import name from A`, then another module C can `import name from B`. Sometimes it is intentional -- module B is meant to "reexport" `name`. But sometimes it is just confusion/inconsistency on where `name` should be imported from. mypy has a flag `--no-implicit-reexport` which puts some order into this. A name can only be imported from a module if 1. The module defines the name 2. The module's `__all__` includes the name 3. The module imports the name as `from ... import .. as name`. This flag is included in mypy's `--strict` flag. I like this flag, but I realize it is a bit controversial, and in particular item 3 above is a bit unfriendly to contributors who don't know about it. So I didn't intend to add it to pytest. But while investigating issue 7589 I came upon mypy issue 8754 which causes `--no-implicit-reexport` to leak into installed libraries and causes some unexpected typing differences *in pytest* if the user uses this flag. Since the diff mostly makes sense, let's just conform to it.
2020-07-31 14:46:56 +08:00
no_implicit_reexport = True