Skip to content

Conversation

@sirosen
Copy link
Member

@sirosen sirosen commented Dec 29, 2025

The overall goal here is to have clearer and more maintainable tox config, without accidentally inheriting things from the default testenv.
Base envs are also a good way to share config explicitly across envs.

  • Add descriptions to all environments.
  • Split the pytest envs off from the default, and make the default fail with a message.
  • Use env inheritance to simplify the pytest env factors.
  • Split up the metadata check environments.
  • Update the default env_list.

Incidentally, add py3.14 to our tox envs (but not added yet in CI, to reduce scope creep).

'tox l' no longer shows environments with no description.
These tests are quick and give us more complete coverage of repo
invariants when `tox p` is run.
An unintended environment name, like `py3.9-mypy` won't run "something":
instead it will explicitly fail.

Using more structured base envs gives the tox.ini file itself a clearer
layout. Allowing this inheritance simplifies the conditional factors in
the testenvs.
This is no longer used for any tox environments. Remove it.
@sirosen sirosen added the no-news-is-good-news This change does not require a news file label Dec 29, 2025
Split 'twine-check' vs 'check-sdist' tox envs so that each check is run
separately (rather than bundled), using environment inheritance to
minimize repetition.

Co-authored-by: Kurt McKee <39996+kurtmckee@users.noreply.github.com>
@sirosen sirosen merged commit c98aa7b into globus:main Dec 29, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-news-is-good-news This change does not require a news file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants