You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both formatters returned what they wrote without reading it, leaving the
file itself as the first thing to try. Each one parses its output now,
and the tox formatter says why it rejects a file rather than handing
back what it was given.
Whitespace between the clauses of `requires-python` says nothing, while
whitespace inside one is what makes the text something PEP 440 does not
read: `> = 3.10` stays as written rather than becoming a constraint the
file never named, and a field this cannot read leaves the classifiers
beside it alone.
A setting read from a TOML table is held to what the command line would
accept, so a negative count, a boolean, or a `table_format` no formatter
knows is reported against the file that names it. Text `tomllib` cannot
read is left to the formatter to report on, rather than reaching the user
as a traceback from a reader that is only there for the settings.
A list the file wrote as a comment names no environment tox runs, so it
no longer decides where the tables that hold them go.
0 commit comments