That would be a policy change. Generally, these sections are for internal use and not part of the public API. If someone really cared about _perfcheck(), the would have tested that function directly. One other thought it that some main sections take arguments, so it stops being a trivial matter to exercise them fully.

Thank you for clarification on non-public status of the script sections. However, I've got a question to remove such a confusion for future others:

Generally, these sections are for internal use and not part of the public API

If they are exclusively for CPython developers and contributors, will it be better to strip them from user-deployed modules and put into a dev-only Tools/? Except for really useful tools like tabnanny (with documented "For the time being this module is intended to be called as a script") that can be granted a public, properly documented argparse-based CLI?