Repository navigation
main branch code cleanups for int_max_str_digits non-backportable TODOs #96512
Description
Activity
Could the limit be a configuration option, so that people who build from source can configure the limit?
Could the limit be a configuration option, so that people who build from source can configure the limit?
Lets have that be its own issue if someone comes up with a compelling use case for it.
My thinking in not including a configure flag to start with is that anyone who builds from source likely also carries patches to their sources so there isn't a good reason to offer a configure option. We don't want to encourage interpreters built and shipped in different environments to have different limits as that can create compatibility headaches for application and library authors potentially expanding their test matrix.
- added a commit that references this issue
on Oct 3, 2022 - added a commit that references this issue
on Oct 3, 2022
I had some post-merge TODOs ready in #96499 for improvements specific to the main (3.12) branch. This is a rollup issue for those, they're all small:
int_max_str_digitsinto PyConfig in 3.12.Useint32_torPy_ssize_tinstead ofintfor the max digits value internally.Minor feature: add PEP-578PySys_Audithook calls at the new ValueError raise spots.