working directory no longer exists.

Thanks to Martin Panter for the bug report.

Issue #22796: HTTP cookie parsing is now stricter, in order to protect against potential injection attacks.

before calling the parent close() method. If the event loop is already closed,
the self-pipe is not unregistered from the selector.

the parent close() method. If the event loop is already closed, the self-pipe
is not unregistered from the selector.

functions:

* add_signal_handler()
* call_at()
* call_later()
* call_soon()
* call_soon_threadsafe()
* run_in_executor()

Fix also the error message of add_signal_handler() (fix the name of the
function).

release mode

- interpreter startup and shutdown code moved to a new
  pylifecycle.c module
- Py_OptimizeFlag moved into the new module with the other
  global flags

Patch by David Watson.

Patch by David Watson.

Based on patch by Franck Michea.

Based on patch by Franck Michea.

Patch by Roumen Petrov.

Patch by Roumen Petrov.

Fixed an error in _PySys_GetSizeOf declaration.

Fixed an error in _PySys_GetSizeOf declaration.

  Patch by Ludovic.Gasc.

  Patch by Ludovic.Gasc.

This auth handler adds the Authorization header to the first
HTTP request rather than waiting for a HTTP 401 Unauthorized
response from the server as the default HTTPBasicAuthHandler
does.

This allows working with websites like https://api.github.com which do
not follow the strict interpretation of RFC, but more the dicta in the
end of section 2 of RFC 2617:

    > A client MAY preemptively send the corresponding Authorization
    > header with requests for resources in that space without receipt
    > of another challenge from the server.  Similarly, when a client
    > sends a request to a proxy, it may reuse a userid and password in
    > the Proxy-Authorization header field without receiving another
    > challenge from the proxy server. See section 4 for security
    > considerations associated with Basic authentication.

Patch by Matej Cepl.