truncation_limit_lines and truncation_limit_chars should accept integer values in .toml configs #14675

Activity

1. Pierre-Sassoulas

   added

   type: enhancementnew feature or API change, should be merged into features branchnew feature or API change, should be merged into features branch

   on Jul 4, 2026
2. bluetech commented on Jul 9, 2026

   

   bluetech

   on Jul 9, 2026

   Member

   More actions

   Due to backward compat, we need to keep supporting string. This means that if we want to allow int, we need to support both.

   @RonnyPfannschmidt had a proposal/draft PR to parse the config based on a pydantic-style class with fields and type annotations. I can't find it quickly right now..

   I had a simpler more short-term idea, that in addition to the current parser.addini(..., type="int") style, we also allow passing a limited set of type expressions to type, so in the case of this issue we could write type=int | str. It seems like a mostly straightforward enhancement to me, though maybe the devil is in the details.

   👍React with 👍1Reacted by Bruno Oliveira
3. bluetech commented on Jul 9, 2026

   

   bluetech

   on Jul 9, 2026

   Member

   More actions

   Forgot to mention regarding the type expression idea. There are some config keys (mostly logging ones IIRC) which mostly take numeric values but are currently str because there is some extra possible string value. For these cases it would be nice to support int Literal["empty"] forms. Also, for typing this the new typing.TypeForm might come in handy (it's new in Python 3.15 but can be imported from typing_extensions on older versions).
4. Pierre-Sassoulas

   added 14 commits that reference this issue on Jul 10, 2026

   Accept int values for truncation limits in TOML config

   ...

   This issue will close once commit 0ae44de is merged into the 'main' branch.

   0ae44de

   Accept int and string truncation limits in TOML config

   ...

   This issue will close once commit 6cf3e85 is merged into the 'main' branch.

   6cf3e85

   Accept int and string truncation limits in TOML config

   ...

   This issue will close once commit 007af70 is merged into the 'main' branch.

   007af70

   Accept int and string truncation limits in TOML config

   ...

   This issue will close once commit c755d27 is merged into the 'main' branch.

   c755d27

   Accept type expressions in Parser.addini(type=...)

   ...

   This issue will close once commit 353934c is merged into the 'main' branch.

   353934c

   Accept int and string truncation limits in TOML config

   ...

   This issue will close once commit 6942da0 is merged into the 'main' branch.

   6942da0

   Accept type expressions in Parser.addini(type=...)

   ...

   This issue will close once commit 412e21b is merged into the 'main' branch.

   412e21b

   Accept int and string truncation limits in TOML config

   ...

   This issue will close once commit 501698d is merged into the 'main' branch.

   501698d

   Accept type expressions in Parser.addini(type=...)

   ...

   This issue will close once commit 52e527f is merged into the 'main' branch.

   52e527f

   Accept type expressions in Parser.addini(type=...)

   ...

   This issue will close once commit fe58d5b is merged into the 'main' branch.

   fe58d5b

   Accept type expressions in Parser.addini(type=...)

   ...

   This issue will close once commit 5ab4b6d is merged into the 'main' branch.

   5ab4b6d

   Accept int and string truncation limits in TOML config

   ...

   This issue will close once commit 5e48fc9 is merged into the 'main' branch.

   5e48fc9

   Accept int and string truncation limits in TOML config

   ...

   This issue will close once commit 3304ed2 is merged into the 'main' branch.

   3304ed2

   Allow int for ``truncation_limit_lines`` and ``truncation_limit_chars…

   ...

   This issue will close once commit f306da7 is merged into the 'main' branch.

   f306da7
5. Pierre-Sassoulas

   closed this as completedin #14692on Jul 31, 2026