delta/cpython-git.git, branch benjamin-tanh-zero github.com: python/cpython.git closes bpo-34640: Remove the TANH_PRESERVES_ZERO_SIGN configure check. 2018-09-12T00:27:37+00:00 Benjamin Peterson benjamin@python.org 2018-09-12T00:27:37+00:00 cb5fa98c9f1810e627b018b2f84e0ecc92deb075 






Delete old expat comment. (GH-9197)
2018-09-12T00:17:39+00:00

Benjamin Peterson
benjamin@python.org

2018-09-12T00:17:39+00:00

b9bf9d025e659b5a1963027eb73690e57cb35dd0












bpo-33649: Cleanup asyncio/streams and asyncio/synchronization docs (GH-9192)
2018-09-12T00:10:37+00:00

Yury Selivanov
yury@magic.io

2018-09-12T00:10:37+00:00

8be876e44b2dffb96b551029454cbfb16d697992












bpo-34605: Replace "pliant children" with "helpers" (GH-9195)
2018-09-11T23:40:06+00:00

Victor Stinner
vstinner@redhat.com

2018-09-11T23:40:06+00:00

fa7dfae3171914f91d629a64c6e829788b485b06

In distutils.command.install, replace "pliant children" (previously,
it was "pliant slaves") with "helpers".

<!-- issue-number: [bpo-34605](https://www.bugs.python.org/issue34605) -->
https://bugs.python.org/issue34605
<!-- /issue-number -->





In distutils.command.install, replace "pliant children" (previously,
it was "pliant slaves") with "helpers".

<!-- issue-number: [bpo-34605](https://www.bugs.python.org/issue34605) -->
https://bugs.python.org/issue34605
<!-- /issue-number -->







Remove configure check LOG1P_DROPS_ZERO_SIGN. (GH-9193)
2018-09-11T23:30:04+00:00

Benjamin Peterson
benjamin@python.org

2018-09-11T23:30:04+00:00

50c99d917c0eded2afcad0a3d7e49475a76440a3

It is unused.

<!--
Thanks for your contribution!
Please read this comment in its entirety. It's quite important.

# Pull Request title

It should be in the following format:

```
bpo-NNNN: Summary of the changes made
```

Where: bpo-NNNN refers to the issue number in the https://bugs.python.org.

Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.

# Backport Pull Request title

If this is a backport PR (PR made against branches other than `master`),
please ensure that the PR title is in the following format:

```
[X.Y] <title from the original PR> (GH-NNNN)
```

Where: [X.Y] is the branch name, e.g. [3.6].

GH-NNNN refers to the PR number from `master`.

-->





It is unused.

<!--
Thanks for your contribution!
Please read this comment in its entirety. It's quite important.

# Pull Request title

It should be in the following format:

```
bpo-NNNN: Summary of the changes made
```

Where: bpo-NNNN refers to the issue number in the https://bugs.python.org.

Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.

# Backport Pull Request title

If this is a backport PR (PR made against branches other than `master`),
please ensure that the PR title is in the following format:

```
[X.Y] <title from the original PR> (GH-NNNN)
```

Where: [X.Y] is the branch name, e.g. [3.6].

GH-NNNN refers to the PR number from `master`.

-->







bpo-1621: Avoid signed integer overflow in set_table_resize(). (GH-9059)
2018-09-11T23:18:01+00:00

Sergey Fedoseev
fedoseev.sergey@gmail.com

2018-09-11T23:18:01+00:00

6c7d67ce83a62b5f0fe5c53a6df602827451bf7f

Address a C undefined behavior signed integer overflow issue in set object table resizing.  Our -fwrapv compiler flag and practical reasons why sets are unlikely to get this large should mean this was never an issue but it was incorrect code that generates code analysis warnings.

<!-- issue-number: [bpo-1621](https://www.bugs.python.org/issue1621) -->
https://bugs.python.org/issue1621
<!-- /issue-number -->





Address a C undefined behavior signed integer overflow issue in set object table resizing.  Our -fwrapv compiler flag and practical reasons why sets are unlikely to get this large should mean this was never an issue but it was incorrect code that generates code analysis warnings.

<!-- issue-number: [bpo-1621](https://www.bugs.python.org/issue1621) -->
https://bugs.python.org/issue1621
<!-- /issue-number -->







closes bpo-31903: Release the GIL when calling into SystemConfiguration (GH-4178)
2018-09-11T23:14:00+00:00

Max Bélanger
aeromax@gmail.com

2018-09-11T23:14:00+00:00

4859ba0d2ce4506fddc3f55f90f8dce031b3804f












bpo-34636: Use fast path for more chars in SRE category macros. (GH-9170)
2018-09-11T22:47:59+00:00

Sergey Fedoseev
fedoseev.sergey@gmail.com

2018-09-11T22:47:59+00:00

ec014a101a7f6243b95dfc08acfe1542b9fa5d39

When handling \s, \d, or \w (and their inverse) escapes in bytes regexes this a small but measurable performance improvement.

<!-- issue-number: [bpo-34636](https://www.bugs.python.org/issue34636) -->
https://bugs.python.org/issue34636
<!-- /issue-number -->




When handling \s, \d, or \w (and their inverse) escapes in bytes regexes this a small but measurable performance improvement.

<!-- issue-number: [bpo-34636](https://www.bugs.python.org/issue34636) -->
https://bugs.python.org/issue34636
<!-- /issue-number -->






Make sure the line comes from the same node as the col offset. (GH-9189)
2018-09-11T22:29:57+00:00

Benjamin Peterson
benjamin@python.org

2018-09-11T22:29:57+00:00

d13e59c1b512069d90efe7ee9b613d3913e79c56

Followup to 90fc8980bbcc5c7dcced3627fe172b0bfd193a3b.

<!--
Thanks for your contribution!
Please read this comment in its entirety. It's quite important.

# Pull Request title

It should be in the following format:

```
bpo-NNNN: Summary of the changes made
```

Where: bpo-NNNN refers to the issue number in the https://bugs.python.org.

Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.

# Backport Pull Request title

If this is a backport PR (PR made against branches other than `master`),
please ensure that the PR title is in the following format:

```
[X.Y] <title from the original PR> (GH-NNNN)
```

Where: [X.Y] is the branch name, e.g. [3.6].

GH-NNNN refers to the PR number from `master`.

-->





Followup to 90fc8980bbcc5c7dcced3627fe172b0bfd193a3b.

<!--
Thanks for your contribution!
Please read this comment in its entirety. It's quite important.

# Pull Request title

It should be in the following format:

```
bpo-NNNN: Summary of the changes made
```

Where: bpo-NNNN refers to the issue number in the https://bugs.python.org.

Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.

# Backport Pull Request title

If this is a backport PR (PR made against branches other than `master`),
please ensure that the PR title is in the following format:

```
[X.Y] <title from the original PR> (GH-NNNN)
```

Where: [X.Y] is the branch name, e.g. [3.6].

GH-NNNN refers to the PR number from `master`.

-->







Revert "bpo-34595: Add %T format to PyUnicode_FromFormatV() (GH-9080)" (GH-9187)
2018-09-11T22:23:25+00:00

Victor Stinner
vstinner@redhat.com

2018-09-11T22:23:25+00:00

998b80636690ffbdb0a278810d9c031fad38631d

This reverts commit 886483e2b9bbabf60ab769683269b873381dd5ee.




This reverts commit 886483e2b9bbabf60ab769683269b873381dd5ee.