pin itsdangerous for python3.6
I wonder how many else will fail. Also it would be nice if the compiled requirements files said where the requirements come from, as in what they are dependencies of, if anything. Like pip-compile does.
This commit is contained in:
parent
fa232daa10
commit
0aa5558888
|
|
@ -16,7 +16,7 @@ hypothesis==6.37.0 ; python_version>="3.7"
|
|||
icdiff==2.0.4
|
||||
idna==3.3
|
||||
iniconfig==1.1.1
|
||||
itsdangerous==2.1.0
|
||||
itsdangerous==2.1.0 ; python_version>="3.7"
|
||||
jaraco.functools==3.5.0 ; python_version>="3.7"
|
||||
# Jinja2==3.0.3
|
||||
Mako==1.1.6
|
||||
|
|
@ -63,3 +63,4 @@ filelock==3.4.1 ; python_version=="3.6.*"
|
|||
hypothesis<6.32 ; python_version=="3.6.*"
|
||||
coverage<6.3 ; python_version=="3.6.*"
|
||||
pytest-mock<3.7 ; python_version=="3.6.*"
|
||||
itsdangerous<2.1.0 ; python_version=="3.6.*"
|
||||
|
|
|
|||
|
|
@ -49,3 +49,5 @@ tldextract
|
|||
#@ add: coverage<6.3 ; python_version=="3.6.*"
|
||||
#@ markers: pytest-mock python_version>="3.7"
|
||||
#@ add: pytest-mock<3.7 ; python_version=="3.6.*"
|
||||
#@ markers: itsdangerous python_version>="3.7"
|
||||
#@ add: itsdangerous<2.1.0 ; python_version=="3.6.*"
|
||||
|
|
|
|||
Loading…
Reference in New Issue