Thanks for the suggestion @laike9m, I think it would be worth opening an issue on bugs.python.org for further discussion of a proposed change to the documentation. For future reference, this topic is best suited towards the “Ideas” section; as it implies a suggested change to Python. I’ll move the topic accordingly.
We typically avoid mentioning every possible edge case in the docs, as it could easily result in an excessive amount of distracting information for readers. The docs focus on the most common cases and are written in consideration of the most useful information for the majority of Python users to be aware of; while maintaining as much accuracy as reasonably possible.
IMO, a better solution would be to modify the wording of the existing description in a way that focuses primarily on the general cases without being entirely incorrect for the edge cases.
The final decision to make any changes or not typically is on the maintainers/experts for the respective section of CPython being changed. In this case, the maintainer of the
inspect module is @yselivanov. I would advise opening a bpo issue, and adding him to the nosy list.
I would also recommend having a specific proposal in mind, detailing the changes you think should be made. This will most likely lead to further discussion, approval, or rejection depending on what Yury (and potentially other core developers) think of the proposed changes.
There is no 100% guaranteed response time (since almost everyone in the Python development community does so voluntarily), but typically you’ll receive a response within a few weeks as long as the proposal itself is very clearly defined and not overly complex.