Improve listenvs behaviour (list completely dynamic environments)

[obestwalter]

#271 missed one possible way of creating environments (completely dynamic just by referencing it in testenv).

[tox]
skipsdist = true

[testenv]
commands =
    dynamicenv: tox --version

tox -a:

python

It shows only the python env which seems to be the standard environment if nothing is defined. This is surprising as IMO creating an env this way is perfectly valid and should behave the same as if I listed it in envlist ...

Expected behaviour would be:

tox -a:

dynamicenv

[hpk42]

On Tue, Apr 18, 2017 at 08:23 -0700, Oliver Bestwalter wrote: #271 missed one possible way of creating environments (completely dynamic just by referencing it in testenv). [tox] skipsdist = true [testenv] commands = dynamicenv: tox --version `tox -a`: python It shows only the `python` env which seems to be the standard environment if nothing is defined. This is a surprising as IMO creating an env this way is perfectly valid and should behave the same as if I listed it in envlist ...

not sure it's a good idea. if you allow implicit definitions of environments then it's harder to catch typos. Right now we are not detecting them directly but you also can not specify them: "tox -e BLABLUB" gives you "unknown environment". Moreover, "dynamicenv" might just be a factor and not a full environment name.

[gaborbernat]

how can that dynamic environment be even invoked?

[obestwalter]

Right now we are not detecting them directly but you also can not specify them: "tox -e BLABLUB" gives you "unknown environment".

Moreover, "dynamicenv" might just be a factor and not a full environment name.

o.k. two showstoppers then basically. Looks like we better put this to an early grave then ...

how can that dynamic environment be even invoked?

The same way 'normal' environments are invoked: the example above woulde be invoked with tox -e dynamicenv.

[obestwalter]

Moreover, "dynamicenv" might just be a factor and not a full environment name.

Just realized that this is not really a showstopper, as we are accounting for that already: you can attach a description to a factor, so this would be not a hindrance. Maybe there is hope ....

[gaborbernat]

another way we miss environments (I just found out is):

[tox]
envlist = py27

[testenv]
passenv = BAS_PROXY http_proxy https_proxy no_proxy
basepython = py27: python2.7
             magic: magic

here magic is not added 🤔

[obestwalter]

That is the same thing though as the dynamicenv example (only defined in a different place). Basically you can create environments wherever just by referencing them.

[gaborbernat]

will take a look at why these are missing 👍

[gaborbernat]

This now has been implemented with tox 4.