venv_redirect was pretty surprising

[thatch]

I'm a little out of the loop and didn't know about the related PEP, but I've written tons of scripts that do something like

if [ ! -e .venv ]; then
  make setup
fi
.venv/bin/python ...

which are now confused by the new enabled-by-default addition. I was wondering if this was an accident, or if the backwards compatibility guarantee is similar to Python, in that the second component is actually treated as the "major" one.

[gaborbernat]

This is unfortunate, but expected. Not much we can do about it. No tool ever guarantees that we won't rely on any future files or paths.Note you can disable global disconfiguration if it bothers you, but the PEP mandates this name to contain this information. One thing you could do is update your scripts to accommodate the PEP.

[thatch]

I could, yes.

One remaining question, is was 4.64 considered a "major" release vs 4.63, or does tox do something different than semver in terms of breaking vs feature releases?

[gaborbernat]

This is not breaking as it's not breaking an existing feature provided by the tool. We never claimed to never generate any other files going ahead.