* Properly handle SyntaxErrors in Python source files.

SyntaxErrors in the target module will rise normally, while SyntaxErrors in dependencies will be added to badmodules. This includes a new regression test.

* Fix name collision bug.

This fixes an issue where a "fromlist" import with the same name as a previously failed import would be incorrectly added to badmodules. This includes a new regression test.

* Replace mutable default values.

Bound empty lists have been replaced with the "if param is None" idiom.

* Replace deprecated imp usage.

Constants imported from imp have been moved to private module-level constants, and ModuleFinder.find_module has been refactored to use importlib. Other than an improvement on how frozen builtin imports are reported (as the frozen imports they are, rather than the stdlib modules they *may* have originated from), these changes maintain complete compatibility with past versions... including odd behavior for returning relative (below current directory, but not a C extension) vs. absolute (above current directory, or a C extension) paths.

Patch by Brandt Bucher.

The shutil archive creation helpers use the default tarfile format,
so that API is also switching to use `pax` by default.

Remove names from the "unimplemented interfaces" list
in the minidom docs that are actually implemented. 

* No need to chunking for now.
* No need to partial read caused by EINTR for now.

Add missing `program` argument to asyncio.create_subprocess_exec documentation.

Use fewer iterations instead of iterating over the whole entry table.

Initialize init_utf8_mode earlier to fix a compiler warning.

The error messages in the parser module are referring to numeric IDs for the nodes. To improve readability, use the node names when reporting errors.

Semantically the same, but more idiomatic by checking against `kwargs` instead of `len(kwargs)`.

bpo-32413: Add documentation that at the module level, locals(), globals() are the  same dictionary (GH-5004)



https://bugs.python.org/issue32413

Incorrect issue number '13210' added in 539ee5da.


https://bugs.python.org/issue13120

I have added documentation for `PyInterpreterState_Main()`.
 I chose to place it under Advanced Debugger Support together with similar functions like `PyInterpreterState_Head()`, `PyInterpreterState_Next(`), and `PyInterpreterState_ThreadHead()` .


https://bugs.python.org/issue36157

Research and fix by @bradlarsen.

set.add(0) and set.add.__get__(0) now raise TypeError
with same error message.

Deprecated passing the following arguments as keyword arguments:

- "func" in functools.partialmethod(), weakref.finalize(),
  profile.Profile.runcall(), cProfile.Profile.runcall(),
  bdb.Bdb.runcall(), trace.Trace.runfunc() and
  curses.wrapper().
- "function" in unittest.addModuleCleanup() and
  unittest.TestCase.addCleanup().
- "fn" in the submit() method of concurrent.futures.ThreadPoolExecutor
  and concurrent.futures.ProcessPoolExecutor.
- "callback" in contextlib.ExitStack.callback(),
  contextlib.AsyncExitStack.callback() and
  contextlib.AsyncExitStack.push_async_callback().
- "c" and "typeid" in the create() method of multiprocessing.managers.Server
  and multiprocessing.managers.SharedMemoryServer.
- "obj" in weakref.finalize().

Also allowed to pass arbitrary keyword arguments (even "self" and "func")
if the above arguments are passed as positional argument.