eval() documentation is wrong about keyword arguments #100546
Description
Activity
Thanks for the report!
cc @JulienPalard the history here is confusing, would you mind posting on #98340 what the current state of using positional-only (and keyword-only) markers in docs is? I still see four positional-only markers in functions.rst (though only eval's seems to be in the wrong place)
Reacted by William AndreaThere are some comments by Raymond on #100444, so one possible guideline for markers is the same for spelling/stylistic rules, where it just needs to be consistent per module instead of for all modules.
That said, I think it'd nonetheless be useful to have a deeper discussion on this for consistency and properly documenting default values, whether it be via markers, or
[], or otherwise.Reacted by Shantanu
Documentation
The docs for
eval()say it takes keyword arguments, which is incorrect:For example:
Meanwhile,
help(eval)has the correct signature:I found a previous, similar issue, #69996, which was resolved in #15173 (which shipped in 3.7) but then the syntax was changed in #96579 and the same sort of mistake was added back (which shipped in 3.11).
This issue is also similar:
Linked PRs