Used in macOS framework builds.

This is a required feature is C99, which we require.

We never actually check HAVE_SELECT.

Fix fileinput with inplace=True to accept pathlib.Path objects.

* Change code owners for hashlib and ssl to the crypto team

* Include the core CSPRNG for the crypto-team

Patch by Paul.j3.  Includes an unrelated but useful addition to the
optparse porting section.

Signed-off-by: Christian Heimes <christian@python.org>

Blurbify master branch.

)

* bpo-1198569: Allow the braced pattern to be different

``string.Template`` subclasses can optionally define ``braceidpattern`` if
they want to specify different placeholder patterns inside and outside the
braces.  If None (the default) it falls back to ``idpattern``.

This comment hasn't been true since Python 3.0.

* Change NPN detection:

Version breakdown, support disabled (pre-patch/post-patch):
- pre-1.0.1: OPENSSL_NPN_NEGOTIATED will not be defined -> False/False
- 1.0.1 and 1.0.2: OPENSSL_NPN_NEGOTIATED will not be defined ->
False/False
- 1.1.0+: OPENSSL_NPN_NEGOTIATED will be defined and
OPENSSL_NO_NEXTPROTONEG will be defined -> True/False

Version breakdown support enabled (pre-patch/post-patch):
- pre-1.0.1: OPENSSL_NPN_NEGOTIATED will not be defined -> False/False
- 1.0.1 and 1.0.2: OPENSSL_NPN_NEGOTIATED will be defined and
OPENSSL_NO_NEXTPROTONEG will not be defined -> True/True
- 1.1.0+: OPENSSL_NPN_NEGOTIATED will be defined and
OPENSSL_NO_NEXTPROTONEG will not be defined -> True/True

* Refine NPN guard:

- If NPN is disabled, but ALPN is available we need our callback
- Make clinic's ssl behave the same way

This created a working ssl module for me, with NPN disabled and ALPN
enabled for OpenSSL 1.1.0f.

Concerns to address:
The initial commit for NPN support into OpenSSL [1], had the
OPENSSL_NPN_* variables defined inside the OPENSSL_NO_NEXTPROTONEG
guard. The question is if that ever made it into a release.
This would need an ugly hack, something like:

	#if defined(OPENSSL_NO_NEXTPROTONEG) && \
		!defined(OPENSSL_NPN_NEGOTIATED)
	#	define OPENSSL_NPN_UNSUPPORTED 0
	#	define OPENSSL_NPN_NEGOTIATED 1
	#	define OPENSSL_NPN_NO_OVERLAP 2
	#endif

[1] openssl/openssl@68b33cc5c7

Broken in GH-2079

…s. (#3312)

See PEP 11.

sys.modules is the one true source.

* bpo-31170: Update libexpat from 2.2.3 to 2.2.4

Fix copying of partial characters for UTF-8 input (libexpat bug 115):
libexpat/libexpat#115

* Add NEWS entry.

…er() received a bad encoder() argument. (#3643)

…ta_setstate() isn't a dictionary. (#3255)

…1569)

now becames exhausted after advancing the groupby iterator.

…3667)

Defer removing old behavior to 3.8.
Document new feature of selection_set() and friends.

A `"` was missing from an `<a href>` tag.

…n_explicit. (#3219)

…bad __name__ global. (#3717)

The dunderless functions are preferred; dunder are retained for back compatilibity.
Patch by Sanket Dasgupta.

Python requires C implementations provide memmove, so we shouldn't need to check for it. The only place using this configure check was expat, where we can simply always define HAVE_MEMMOVE.

…methods (#3739)

…_(), in case of a bad __dict__. (#3254)

Non-regression tests for the Expat 2.2.3 UTF-8 decoder bug.

)

GH-3711)

…H-3691)

- Remove the second mention about the `u` prefix
- Remove the second mention about numeric literals do not include a sign

…3753)

…pby() iterators. (#1557)

…fig.sh (#3769)

Fix the logic in python-config.sh to avoid attempting to substitute
prefix in a variable that might have already been subject to
substitution. This e.g. happened if @exec_prefix@ was defined as
"${prefix}" (which is the default of the configure script) -- in which
case the exec_prefix_build variable was initialized with
already-subtituted prefix, and then another round of substitution was
performed which might have resulted in duplicate prefix.

To avoid that, rename the variables so that the variables matching
likely configure names (prefix, exec_prefix) retain their original
values and a '_real' suffix is used for the real values of prefix.

Furthermore, replace the unnecessary prefix and exec_prefix
substitutions with direct prefix_real references since the sed
always replaced the whole string anyway by design.

…thread (#3782)

Class execution requires that __prepare__() methods return
a proper execution namespace. Check for that immediately
after calling __prepare__(), rather than passing it through
to the code execution machinery and potentially triggering
SystemError (in debug builds) or a cryptic TypeError
(in release builds).

Patch by Oren Milman.

…as a bad __abs__() method. (#3596)