Fix tox.ini parse error with tox 4.2.8
The validation of setenv in the recent tox like 4.2.8 seems more strict. We need a space between a factor and envvar. Note that we need to discuss the three variants of PYTHONWARNINGS but this commit focuses on fixing the gate failure due to tox.ini. Change-Id: I13be2d39850e77f15e5bbf67b0022b10b09e5c6f
This commit is contained in:
parent
aec6340398
commit
20966c4968
2
tox.ini
2
tox.ini
@ -14,7 +14,7 @@ setenv =
|
|||||||
PYTHONDONTWRITEBYTECODE = 1
|
PYTHONDONTWRITEBYTECODE = 1
|
||||||
# TODO(amotoki): There are three variants of PYTHONWARNINGS. They should be merged.
|
# TODO(amotoki): There are three variants of PYTHONWARNINGS. They should be merged.
|
||||||
PYTHONWARNINGS = once,ignore::PendingDeprecationWarning
|
PYTHONWARNINGS = once,ignore::PendingDeprecationWarning
|
||||||
py{3,39}:PYTHONWARNINGS = once,ignore::PendingDeprecationWarning,ignore::ImportWarning:backports
|
py{3,39}: PYTHONWARNINGS = once,ignore::PendingDeprecationWarning,ignore::ImportWarning:backports
|
||||||
# DeprecationWarning is disabled in dj32 tox env as Django 3.2
|
# DeprecationWarning is disabled in dj32 tox env as Django 3.2
|
||||||
# deprecated Django 2.2 features. This workaround is just to reduce
|
# deprecated Django 2.2 features. This workaround is just to reduce
|
||||||
# the number of warnings due to this change.
|
# the number of warnings due to this change.
|
||||||
|
Loading…
Reference in New Issue
Block a user