Windows has no memrchr() function.

This change is only a workaround, the optimization must be reenabled on other
platforms.

close the binary file to fix a resource warning.

Flushing sys.stdout and sys.stderr in Py_FatalError() can call again
Py_FatalError(). Add a reentrant flag to detect this case and just abort at the
second call.

Flushing sys.stdout and sys.stderr in Py_FatalError() can call again
Py_FatalError(). Add a reentrant flag to detect this case and just abort at the
second call.

writer failed in BufferedRWPair.close().

writer failed in BufferedRWPair.close().

and ASCII letter now raise a deprecation warning and will be forbidden in
Python 3.6.

keyword argument.  string.Formatter now allows to specify the "self" and
the "format_string" parameters as keyword arguments.

keyword argument.  string.Formatter now allows to specify the "self" and
the "format_string" parameters as keyword arguments.

str.index, str.count, the in operator, str.split, str.partition) with
arguments of different kinds (UCS1, UCS2, UCS4).

In particular the __dict__ attributes of building types.

extesible.  No public API is added.

Got rid of quadratic complexity in breaking long words.

https://twitter.com/ncoghlan_dev/status/579173053793353728

supports copying of instances of classes whose __new__ method takes
keyword-only arguments.

Too bad, sometimes Py_FatalError() is unable to write the exception into
sys.stderr (on "AMD64 OpenIndiana 3.x" buildbot, the buildbot was probably out
of memory).

Call Py_FatalError() with a different message for the two cases (result+error,
or no result and no error).

sys.stderr

It should help to see exceptions when stderr if buffered: PyErr_Display() calls
sys.stderr.write(), it doesn't write into stderr file descriptor directly.

It should help to see exceptions when stderr if buffered: PyErr_Display() calls
sys.stderr.write(), it doesn't write into stderr file descriptor directly.

Py_FatalError() instead of using an assertion in debug mode. Py_FatalError()
displays the current exception and the traceback which contain more information
than just the assertion error.

current exception because they can run arbitrary Python code and so no
exception must be set.

I expected more users of _Py_wstat(), but in practice it's only used by
Modules/getpath.c. Move the function because it's not needed on Windows.
Windows uses PC/getpathp.c which uses the Win32 API (ex: GetFileAttributesW())
not the POSIX API.

* Display the current Python stack if an exception was raised but the exception
  has no traceback
* Disable faulthandler if an exception was raised (before it was only disabled
  if no exception was raised)
* To display the current Python stack, call PyGILState_GetThisThreadState()
  which works even if the GIL was released

* Display the current Python stack if an exception was raised but the exception
  has no traceback
* Disable faulthandler if an exception was raised (before it was only disabled
  if no exception was raised)
* To display the current Python stack, call PyGILState_GetThisThreadState()
  which works even if the GIL was released