Fix CI failures By remove `tox-direct`

[ffgan]

I've been working on adding riscv64 support to the current project, which has been straightforward so far. However, I noticed that the recent CI runs aren't fully passing—specifically, some Actions are failing.

After a quick analysis, the issue seems to stem from this commit, which introduced dependency_groups. This is causing problems with tox.

While tox added support for dependency_groups (as described in issue #3408), our current setup is restricted by tox-direct, which limits us to tox < 4. Since tox requires version 4.22.0 or higher to support dependency groups, the CI is failing.

Given that tox-direct hasn't been updated in a long time, should we consider removing it? I’ve tested this, and the CI passes once it's removed. However, I’m not sure why tox-direct was originally used to bypass tox's managed virtual environments, so I’m opening this issue to discuss the situation.

---

Other Info
Co-authored-by: Jincheng Ni nijincheng@iscas.ac.cn

[ionelmc]

The idea with tox-direct was that the envs that build the wheels that end up in PyPI test exactly those wheels, bit by bit. I am not against removing tox-direct but I want those wheels tested. I dont want to run tests and then build wheels, or build wheels but run test on some other wheels that tox builds internally - that would make testing pointless.

[ionelmc]

I didn't notice dependency_groups is incompatible with the version requirements of tox-direct, would reverting that change suit you?

[ffgan]

The idea with tox-direct was that the envs that build the wheels that end up in PyPI test exactly those wheels, bit by bit. I am not against removing tox-direct but I want those wheels tested. I dont want to run tests and then build wheels, or build wheels but run test on some other wheels that tox builds internally - that would make testing pointless.

I'm not very familiar with tox, but I believe there should be a mature solution for this issue in tox. Perhaps we could open an issue in tox to ask about it.

[ffgan]

I didn't notice dependency_groups is incompatible with the version requirements of tox-direct, would reverting that change suit you?

It's better to keep it as is, after all, it's an issue with tox-direct, not with the dependency_groups.

[ffgan]

The idea with tox-direct was that the envs that build the wheels that end up in PyPI test exactly those wheels, bit by bit. I am not against removing tox-direct but I want those wheels tested. I dont want to run tests and then build wheels, or build wheels but run test on some other wheels that tox builds internally - that would make testing pointless.

pypa/cibuildwheel#1504 , what about this?

[ionelmc]

That might work, feel free to try it. Note that https://github.com/ionelmc/python-lazy-object-proxy/blob/master/.github/workflows/github-actions.yml is generated from https://github.com/ionelmc/python-lazy-object-proxy/blob/master/ci/templates/.github/workflows/github-actions.yml (by running either tox -e bootstrap or ./ci/bootstrap.py).

[ffgan]

That might work, feel free to try it. Note that https://github.com/ionelmc/python-lazy-object-proxy/blob/master/.github/workflows/github-actions.yml is generated from https://github.com/ionelmc/python-lazy-object-proxy/blob/master/ci/templates/.github/workflows/github-actions.yml (by running either tox -e bootstrap or ./ci/bootstrap.py).

https://github.com/ffgan/python-lazy-object-proxy/actions/runs/21396261601/job/61595224599. What about this.

[ffgan]

https://github.com/ffgan/python-lazy-object-proxy/actions/runs/21396261601/job/61595224599. What about this.

see this commit, ffgan@089fd49

[ionelmc]

Looks good, make a PR. Can you also remove this stuff (looks like some leftovers from when 3.14 wasn't fully released):

{% elif prefix.startswith('py314') %}
{% set python %}3.14.0-rc.2{% endset %}
{% set cpython %}cp314{% endset %}