Skip to content

Conversation

@ferdnyc
Copy link
Contributor

@ferdnyc ferdnyc commented Dec 2, 2025

A very minor documentation addition.

Tox's ultra-concise environment naming creates some challenges when using features like range expansions. If the user tries to define a range like py{39-314}, they'll get a lot more than they bargained for. Add a "Caution" box to the documentation about the range feature, reminding users to consider what their ranges mean numerically, rather than semantically.

  • ran the linter to address style issues (tox -e fix)
  • wrote descriptive pull request text
  • ensured there are test(s) validating the fix
  • added news fragment in docs/changelog folder
  • updated/extended the documentation

Tox's ultra-concise environment naming creates some challenges when
using features like range expansions. If the user tries to define
a range like `py{39-314}`, they'll get a lot more than they bargained
for. Add a "Caution" box to the documentation about the range feature,
reminding users to consider what their ranges mean _numerically_,
rather than semantically.

Signed-off-by: FeRD (Frank Dana) <ferdnyc@gmail.com>
@ferdnyc ferdnyc requested a review from gaborbernat as a code owner December 2, 2025 01:39
@gaborbernat gaborbernat merged commit 43e2d98 into tox-dev:main Dec 4, 2025
27 of 28 checks passed
@ferdnyc ferdnyc deleted the docs-caution branch December 4, 2025 21:36

Be conscious of the number of significant digits in your range endpoints.
A range like ``py{39-314}`` will not do what you may expect.
(It expands to 275 environment names,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's gonna bug me that that should've been 276. 🙄

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.

2 participants