Replies: 1 comment
-
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'd like to run a tox env with an additional constraint on the dependencies. I'd like to do that directly in the invocation, either by specifying a command-line parameter or setting an environment variable.
Based on these docs:
Since
package
is defined at the same level asdeps
, I'd have expected that settingTOX_DEPS
would have allowed overriding thetestenv.deps
, but it didn't. I also triedTOX_ENV_DEPS=pydantic>=2
andTOX_TEST_ENV_DEPS
andTOX_TESTENV_DEPS
, but none have any effect.I also tried
tox run -e py -x 'deps=pydantic>=2'
along with other variants for-x
, includingtestenv:py.deps=pydantic>=2
, but none had any effect.The current config specifies
deps=
, so overriding or extending requirements functions the same in this case, though what I really want is to constrain. What I don't want to do is have to generate a file (and clean it up later) in order to test.Is this objective achievable with tox? Why are the documented expectations not met?
Beta Was this translation helpful? Give feedback.
All reactions