The one interface we commit to maintain is the run module
(a.k.a. the pysetup script).

Running with regrtest does not show spurious output or unrestored
sys.std* objects; sometimes running with make test is different, I’ll
watch the buildbots.

In addition, update the create module to use logging.

When an option is changed on a command object, calling ensure_finalized
for a second time will not run finalize_options again, because
ensure_finalized is a no-op the second time.  By resetting the finalized
attribute, we can be sure that whatever computation takes place in
finalize_options will happen again.

(In test_command_clean, I removed two lines that were a no-op.)

This method was named reinitialize_command in distutils and accompanied
by a comment suggesting to change it to get_reinitialized_command.
Following that, I did the change for distutils2, but it proved
confusing: The Distribution object has an internal cache of command
objects, to make sure only one instance is ever used, and the name
get_reinitialized_command could suggest that the object returned was
independent of that cache, which it was not.  I’m reverting the name
change to make code clearer.

to poll(2): don't set them.

Closes #13254.

Closes #13254.

variable in the default value of a keyword-only argument:
(lambda *, arg=GLOBAL_NAME: None)

variable in the default value of a keyword-only argument:
(lambda *, arg=GLOBAL_NAME: None)

_PyUnicode_CheckConsistency() checks also hash and length value for not ready
Unicode strings.

Thanks to Robert Xiao.

 * _PyUnicode_CheckConsistency() now takes a PyObject* instead of void*
 * Remove now useless casts to PyObject*