| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| | |
Allow user to inject specific Pythons to try as step 1 during discovery
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
At the moment it's unecessarily hard to specify a specific python
executable to use for a given spec. While mangling with the path
might work for environments for tox environments that require a python
differing the host tox python version; for environments matching the
host tox interpreter it's impossible to use any other interpreter than
what tox uses. Here we add a CLI argument (fallback to some environment
variable for CI usage) that allows the user to inject custom python
interpreters as step 1 of the discovery mechanism.
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
|
| | |
|
| |\
| |
| | |
release 3.14.4
|
| |/ |
|
| |
|
|
|
| |
Avoids problem introduced by newer virtualenv which broke installation
of tox on systems that already had a six version >1.0 installed but
which was older than minimal needed by tox.
|
| |
|
|
|
|
|
|
|
|
| |
* Adding correct dependency and import for pytest
* fix unused import
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
Co-authored-by: Bernát Gábor <gaborjbernat@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Avoid pypy test failure due to undefined printout var
Fixes CI error seen with other patches.
* provision pypy3 on pypy
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
Co-authored-by: Bernát Gábor <gaborjbernat@gmail.com>
|
| | |
|
| | |
|
| | |
|
| |
|
| |
In #1283, the 'download' option was added, but without documentation.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default, we run SIGKILL after 0.5 seconds. Most of the time is
enough. But if the interrupted command have a complex processes tree,
it might not be enough to propagate the signal.
In such case processes are left behind and never killed.
If theses processes use static network port or keep file open. Next
call of tox will fail until the all processes left behind are manually
killed.
This change adds some configuration to be able to config the timeout
before signals are sent.
If the approach work for you, I will polish the PR (doc+test)
|
| | |
|
| |\
| |
| | |
release 3.14.3
|
| |/
|
|
| |
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
|
| |
|
|
|
|
|
|
| |
* Update guide with instructions to disable spinner
This is in the command-line help, but can't be found anywhere obvious in the documentation.
* Oops, delete trailing space
|
| |
|
| |
a follow up to #1467
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Mark poetry tests as xfail on windows
* Update tests/integration/test_package_int.py
Co-Authored-By: Anthony Sottile <asottile@umich.edu>
* fix formatting
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
|
| |
|
|
|
|
| |
* use get_python_info for consistency and caching
* changelog
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Fixes #1428
When running in Jenkins and using `setup.cfg`, tox would not fall back
to the [tox:tox] configuration properly. This was due to how the
fallback section name was calculated in this specific combination of
characteristics.
on-behalf-of: @ithaka <dane.hillard@ithaka.org>
|
| |
|
|
|
|
| |
pytest-mock 1.11.2 raises:
> ValueError: Using mocker in a with context is not supported.
> https://github.com/pytest-dev/pytest-mock#note-about-usage-as-context-manager
|
| |\
| |
| | |
release 3.14.1
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
| |
* fix
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
* suppress proc related failures on pypy
Signed-off-by: Bernat Gabor <bgabor8@bloomberg.net>
|
| |
|
|
|
|
|
|
|
| |
This shouls avoid SSL failures with HTTP requests from pip, requests
or other libraries.
Also sorts existing values in order to make it easier to update the
list in the future.
Fixes: #1437
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the original interpreter [0] tox is called with is actually a pyvenv
it will set the `__PYVENV_LAUNCHER__` environment variable to the path of
pyvenv interpreter.
If tox configuration specifies `requires` and the requirements are not
satifsfied by [0], tox will create an intermediate virtual environment [1].
After setting up [1] tox will delegate the original call by spawning
a new [1] interpreter with the identical identical list of arguments.
It will also pass the value of `__PYVENV_LAUNCHER__` if present. This in turn
causes `sys.executable` to resolve to [0] instead of [1] therefore ignoring all
modifications including installed requirements.
The fix is to make sure that when [0] spawns [1], `__PYVENV_LAUNCHER__` is
removed from the environment.
|
| |
|
|
|
|
| |
`subprocess` reports a negative exit code for signals.
Still handle "128 + X" for processes indicating that they received a
signal themselves.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...but keep the TOX_PARALLEL_ENV variable for others to consume.
The problem with using environment variables to let tox know it's being run
as a parallel worker is the following:
Either you don't pass the environment variable, but the test frameworks and
test suites are unaware that tox is running in parallel.
This makes it hard for cases like pytest-django:
https://github.com/tox-dev/tox/pull/1139
Or you pass the environment variable, but it makes tox invoked within tox
think it is a parallel worker even when it isn't.
This makes it hard to test various tox plugins that invoke tox in their
integration test suite:
Fixes https://github.com/tox-dev/tox/issues/1444
By introducing two variables we can use one ("private", _TOX_PARALLEL_ENV) to
control the behavior of tox (and don't pass it) and another ("public",
TOX_PARALLEL_ENV) to let the tests and test frameworks know tox is running
in parallel (and pass it by default).
The integration test is a tad complicated invoking subprocess.Popen instead
of subprocess.run, to support Python 2.7 and 3.4.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* Upgrade minimal virtualenv version to 16.0.0
Fixes #1425
* Add a change note about the virtualenv bump
|
| | |
|
| |\
| |
| | |
release 3.14.0
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
| |
As identified by Debian's lintian:
- comand -> command
- suceeds -> succeeds
- intepreter -> interpreter
- allow(s) to -> allow(s) you/one to
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* 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)
|
| | |
|
| | |
|
| | |
|
