Skip to content

[BUG] Tox script does not run the intended Python interpreter for each environment #1834

@amahussein

Description

@amahussein

Describe the bug

The tox.ini does not correctly use the correct the python interpreter. It creates a separate folder for each python, but those folders eventually have the same packages as the base python.
It seems that the problem is that tox falls-back to the default interpreter because it cannot find the other python on PATH. This is due to using virtual-env like pyenv.

What we need to explore:

Find a way to configure tox to use the virtual-env engine if possible in order to correctly use it.
Of course, this requires that the python-iterpreter is already installed before running the script.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ? - Needs TriagebugSomething isn't workingtestFor issues or changes related to unit-tests or testing in general.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions