Skip to content

chore: use native pyproject config for tox and pytest - #490

Merged
nandgator merged 1 commit into
masterfrom
config-native-tox-and-pytest
Oct 10, 2026
Merged

nandgator merged 1 commit into
masterfrom
config-native-tox-and-pytest

Conversation

@nandgator

Copy link
Copy Markdown
Collaborator

Summary

  • Replace legacy_tox_ini with native [tool.tox] tables (tox>=4.22), keeping the same environments: lint, type, format, sast and py311 to py314. The type and unit-test envs install the crypto-eth-addresses extra through extras.
  • Replace [tool.pytest.ini_options] with the native [tool.pytest] table (needs pytest 9.0 or later).
  • Raise the dev dependency floors to match (tox>=4.22, pytest>=9.0.3), then relock with pdm and re-export package/requirements.*.txt. No pin was downgraded; only packaging and pluggy moved, both forward.
  • Other tool configs (ruff, pyright, bandit, setuptools) were already native.

Test plan

  • tox -e py311,py312,py313,py314,type,lint,sast all pass (1029 tests per interpreter including doctests)
  • export man and export web build with no warnings and no diffs to committed docs; the man page renders
  • CI

🤖 Generated with Claude Code

Replace legacy_tox_ini with native [tool.tox] tables (tox>=4.22) and
[tool.pytest.ini_options] with native [tool.pytest] (pytest>=9.0).
Raise the dev dependency floors to match, then relock with pdm and
re-export package/requirements.*.txt.
@nandgator
nandgator merged commit c615278 into master Oct 10, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant