Confusing virtualenv interpolation tox 3.24 #2331
-
tox 3.24.1 My question is: why, if I use {toxinidir}{/}{envpython} to convey the absolute path of the virtualenv python interpreter used, does the resulting path become the toxinidir path followed by the now-absolute path for {envpython}? Is it a design feature that whenever the interpolation has non-whitespace before the reference, it's converted to an absolute path? And as you can see from the tox -v -v feedback below, if {envpython} is argv[0] for the command, its full path is used.
And, as pointed out by @tucked, the tox -v -v output is somewhat misleading, if just {envpython} is used, the relative path is conveyed. But mixed feedback from tox [ fyi: {envtmpdir}{/}kernels is the tox.ini argument for the below --dir option, I used --tmp mytemp:{envtmpdir} to see what happens for that variable if non-whitespace before the reference - same misleading feedback] commands in commands_pre= section:
MTIA for any insights, feedback. And yes, I'm hoping to update to tox 4 'soon' :-). Tox is quite powerful, useful. Much appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I don't think your use case was designed per se. The way it works is mostly because happens to work like that 🤔 Furthermore, there's not much we can do here, tox 3 is mostly frozen at this point feature wise. |
Beta Was this translation helpful? Give feedback.
I don't think your use case was designed per se. The way it works is mostly because happens to work like that 🤔 Furthermore, there's not much we can do here, tox 3 is mostly frozen at this point feature wise.