1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
|
# NOTE: `apipkg` has broken the support of Python 3.4, seemingly
# NOTE: accidentally. It's a transitive dependency for us, through
# NOTE: `pytest-xdist` -> `execnet`.
# Ref: https://github.com/pytest-dev/apipkg/issues/29
apipkg != 2.1.0; python_version == "3.4"
# chardet is a dependency of requests. It is optional under
# Python 3 but is used if present. Starting with requests v2.26.0,
# requests depends on charset_normalizer that emits a warning in
# our tests:
# ```
# UserWarning: Trying to detect encoding from a tiny portion
# of (12) byte(s).
# ```
# Ref: https://github.com/psf/requests/commit/2ed84f5
# To avoid the warning, we declare a direct dependency on chardet
# here so that it's use is adjusted across Python 2 and Python 3:
requests[use_chardet_on_py3]
# Updating `charset-normalizer` on Python 3.5 under Ubuntu 18.04 causes
# some weird issues with `cryptography` — it starts wanting `libffi7`
# but only `libffi6` is available in that environment.
# Note that there's no `charset-normalizer` for Python 2
charset-normalizer < 2.1.0; python_version >= "3.0" and python_version <= "3.5"
# Address https://github.com/tartley/colorama/issues/240.
# It's a transitive dependency of pytest-watch plugin.
colorama!=0.4.2; python_version == "3.4"
# measure test coverage
coverage >= 6.2; python_version >= "3.6"
coverage < 5; python_version == "3.4"
coverage < 6; python_version < "3.6" and python_version != "3.4"
futures; python_version == "2.7"
jaraco.context
jaraco.text>=3.1
portend
# cryptography >= 3.4 started using Rust but it's unstable w/ old PyPy
# and pyopenssl == 22 started requiring cryptography 35+
# which is why we need these restrictions for the dependency resolution
# to succeed.
pyopenssl; implementation_name != "pypy"
pyopenssl >= 22.0.0; implementation_name == "pypy" and python_version >= "3.8"
pyopenssl < 22.0.0; implementation_name == "pypy" and python_version < "3.8"
# The pypytools library provides a cross-implementation context
# manager for disabling garbage collection in specific blocks
# of the control flow:
pypytools
pytest-cov==2.8.1; python_version == "3.4" # pyup: < 2.9
pytest-cov==2.12.0; python_version != "3.4"
pytest-forked>=1.1.3; sys_platform != "win32" and python_version >= '3.0' and python_version <= '3.4'
pytest-forked>=1.2.0; sys_platform != "win32" and (python_version < '3.0' or python_version > '3.4')
pytest-mock>=1.11.0
pytest-rerunfailures < 9; python_version <= "2.7" or python_version == "3.4"
pytest-rerunfailures < 10; python_version == "3.5"
pytest-rerunfailures; python_version >= "3.6"
pytest-sugar>=0.9.3
pytest-watch==4.2.0
pytest-xdist>=1.28.0
# pytest-forked is currently incompatible with pytest 7
pytest >= 4.6.6, < 7
# HTTP over UNIX socket
requests-unixsocket
requests_toolbelt
# TLS
trustme>=0.4.0
urllib3<1.25; python_version == "3.4" # pyup: < 1.25
# This addresses https://github.com/cherrypy/cheroot/issues/173.
# It's a transitive dependency of requests library.
# Also: requests>=2.22.0 doesn't support Python 3.4
# yet requests==2.21.0 doesn't support urllib3>=1.25
# Allowing requests with a lower urllib3 version
# so that tests'd pass
urllib3>=1.25; python_version != "3.4"
watchdog<1.0.0; python_version < "3.6"
# cryptography >= 3.4 started using Rust but it's unstable w/ old PyPy
cryptography < 3.4; implementation_name == "pypy" and python_version < "3.8"
|
