You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off thank you very much for the great work on the package!
I have always assumed that recreate = false implied that a tox environment would not be recreated if it exists already. It was thus a bit confusing to see my existing environment recreated sometimes nonetheless. For example it happens if I run Tox from the command line, and subsequently in Pycharm via Tox configuration (same configuration).
After some debugging, I discovered that I need to run tox with the python executable that initially created my environment in order to avoid recreating it. The environment path appears to be defined in the .tox-config1 file.
In my example above, Pycharm automatically activates the executable called pythonX.X in its command line tool, while it uses the executable called python when you run it via a Tox configuration.
What's the rationale behind ensuring that the same executable is used to prevent recreating an environment?
Additionally, I was wondering if it was possible to add a line or two in the documentation of the recreate config field to explain that false does not mean that the environment will not be recreated (for example if tox is called from another python)?
I use tox 3.12.1
Thank you,
PJ
The text was updated successfully, but these errors were encountered:
Thanks for the report - tox has several ways trying to figure out, if it is necessary to recreate the environment, so setting recreate to false basically just means preserve the default behaviour (which is let tox guess if it should recreate the environment). Whereas set to true it actually means always force recreation. Im hindsight, maybe that flag would better have been called --force-recreate or something.
I was wondering if it was possible to add a line or two in the documentation of the recreate config field to explain that false does not mean that the environment will not be recreated (for example if tox is called from another python)?
* clarify behaviour if recreate is set to false in config.rst (#1372)
* added file to changelog (#1372)
* add new line at the end of changelog entry (#1372)
Hi guys,
First off thank you very much for the great work on the package!
I have always assumed that
recreate = false
implied that a tox environment would not be recreated if it exists already. It was thus a bit confusing to see my existing environment recreated sometimes nonetheless. For example it happens if I run Tox from the command line, and subsequently in Pycharm via Tox configuration (same configuration).After some debugging, I discovered that I need to run tox with the python executable that initially created my environment in order to avoid recreating it. The environment path appears to be defined in the .tox-config1 file.
In my example above, Pycharm automatically activates the executable called pythonX.X in its command line tool, while it uses the executable called python when you run it via a Tox configuration.
What's the rationale behind ensuring that the same executable is used to prevent recreating an environment?
Additionally, I was wondering if it was possible to add a line or two in the documentation of the
recreate
config field to explain thatfalse
does not mean that the environment will not be recreated (for example if tox is called from another python)?I use tox 3.12.1
Thank you,
PJ
The text was updated successfully, but these errors were encountered: