Environment variables containing strings with spaces are not accepted any longer for passenv/pass_env.

[Marc2508]

Looks like this change:
#2658
causes an error for environment variables that are strings:
py3: failed with pass_env values cannot contain whitespace, use comma to have multiple values in a single line, invalid values found '-m "not scale"'

export PYTEST_ARGS = '-m "not scale"'

passenv =
{env:PYTEST_ARGS}

Is this intended?

[mgedmin]

This seems like weird syntax. If you want PYTEST_ARGS to be passed to the commands executed by tox, you would put

pasenv = PYTEST_ARGS

in the tox.ini. Why are you using {env:PYTEST_ARGS}? {env:...} is for including the value of the environment variable into tox configuration.

[gaborbernat]

This seems like a broken configuration where the validation caught it. You're welcome 😊

[Marc2508]

Thanks for the fast response and your help!
The problem was indeed {env:PYTEST_ARGS} instead of just using PYTEST_ARGS. The PYTEST_ARGS are actually exported by an external Makefile so I assume the {env:PYTEST_ARGS} expression was chosen to read this environment variable. This was working in general but it seems to remove the quotes around the expression.

[mkoeppe]

My tox.ini files are also affected by the change to the parsing of passenv in tox 4:
I can no longer use factors to conditionalize which environment variables are passed:

passenv =
    sagepython, sagewheels:  SAGE_VENV
    sagewheels:              SAGE_SPKG_WHEELS

(from https://github.com/sagemath/sage/blob/develop/pkgs/sagemath-categories/tox.ini#L29)

[gaborbernat]

This is unrelated to the question here; you should open an issue for it.

[mkoeppe]

That's now #2718