Fix a crash when a generator is created in a C thread that is destroyed while
the generator is still used. The issue was that a generator contains a frame,
and the frame kept a reference to the Python state of the destroyed C thread.
The crash occurs when a trace function is setup.

crash when a generator is created in a C thread that is destroyed while the
generator is still used. The issue was that a generator contains a frame, and
the frame kept a reference to the Python state of the destroyed C thread. The
crash occurs when a trace function is setup.

has no concrete GIL. If PyGILState_Ensure() is called from a new thread for the
first time and PyEval_InitThreads() was not called yet, a GIL needs to be
created.

This fixes running test_decimal in verbose mode on Windows,
which I broke in issue #19572.

There are enough new things to make the merge harder than making the
change in VS, and there are other things to add filters for in 3.4.

Also, cleaned up an unused import.

This version of the fix raises an error instead of accepting the invalid
input (ie: if a non-ASCII string is used but no charset is specified).

This is a backward compatible partial fix, the complete fix requires raising
an error instead of accepting the invalid input, so the real fix is only
suitable for 3.4.

return not int instance.  Introduced _PyLong_FromNbInt() and refactored
PyLong_As*() functions.

return not int instance.  Introduced _PyLong_FromNbInt() and refactored
PyLong_As*() functions.

fix to Issue #14635 in Python 3.3.0 to be interpreted as milliseconds instead
of seconds when the platform supports select.poll (ie: everywhere).  It is now
treated as seconds once again.

shell window is present. (Original patch by Terry Reedy)

The stdlib docs for package distribution and building extensions
are rather dated, and that isn't expected to change for 2.7 and
3.3.

The Python Packaging User Guide isn't complete either, but it's
already a much better road map for new users than the existing
stdlib docs.