delta/cpython-git.git/aclocal.m4, branch fix-namedexpr-comment github.com: python/cpython.git bpo-34652 again: Remove lchmod from the default AC_CHECK_FUNCS list. (GH-15758) 2019-09-09T12:13:00+00:00 Benjamin Peterson benjamin@python.org 2019-09-09T12:13:00+00:00 bed04b664729e3e6fcee42daa108936360bac6ea 






bpo-26826: Expose copy_file_range in the os module (GH-7255)
2019-05-31T18:39:47+00:00

Pablo Galindo
Pablogsal@gmail.com

2019-05-31T18:39:47+00:00

aac4d0342c3e692731c189d003dbd73a8c681a34















bpo-26836: Add os.memfd_create() (#13567)
2019-05-29T19:57:03+00:00

Zackery Spytz
zspytz@gmail.com

2019-05-29T19:57:07+00:00

43fdbd2729cb7cdbb5afb5d16352f6604859e564

* bpo-26836: Add os.memfd_create()

* Use the glibc wrapper for memfd_create()

Co-Authored-By: Christian Heimes <christian@python.org>

* Fix deletions caused by autoreconf.

* Use MFD_CLOEXEC as the default value for *flags*.

* Add memset_s to configure.ac.

* Revert memset_s changes.

* Apply the requested changes.

* Tweak the docs.





* bpo-26836: Add os.memfd_create()

* Use the glibc wrapper for memfd_create()

Co-Authored-By: Christian Heimes <christian@python.org>

* Fix deletions caused by autoreconf.

* Use MFD_CLOEXEC as the default value for *flags*.

* Add memset_s to configure.ac.

* Revert memset_s changes.

* Apply the requested changes.

* Tweak the docs.







bpo-33164: update blake2 implementation (GH-6286)
2019-05-23T04:32:44+00:00

David Carlier
dcarlier@afilias.info

2019-05-23T04:32:44+00:00

51aa35e9e17eef60d04add9619fe2a7eb938358c












Run autoreconf.
2019-02-26T05:37:59+00:00

Benjamin Peterson
benjamin@python.org

2019-02-26T05:37:59+00:00

b84df2d7cc755b6097cfcd3b1515035844590545












bpo-35674: Add os.posix_spawnp() (GH-11554)
2019-01-16T13:29:26+00:00

Joannah Nanjekye
33177550+nanjekyejoannah@users.noreply.github.com

2019-01-16T13:29:26+00:00

92b8322e7ea04b239cb1cb87b78d952f13ddfebb

Add a new os.posix_spawnp() function.




Add a new os.posix_spawnp() function.






bpo-28015: Support LTO build with clang (GH-9908)
2018-10-24T23:54:22+00:00

serge-sans-paille
serge.guelton@telecom-bretagne.eu

2018-10-24T23:54:22+00:00

5ad36f9b21a3aa3b2265b1b43d73522cc3322df2

.o generated by clang in LTO mode actually are LLVM bitcode files, which
leads to a few errors during configure/build step:

- add lto flags to the BASECFLAGS instead of CFLAGS, as CFLAGS are used
  to build autoconf test case, and some are not compatible with clang LTO
  (they assume binary in the .o, not bitcode)
- force llvm-ar instead of ar, as ar is not aware of .o files generated
  by clang -flto




.o generated by clang in LTO mode actually are LLVM bitcode files, which
leads to a few errors during configure/build step:

- add lto flags to the BASECFLAGS instead of CFLAGS, as CFLAGS are used
  to build autoconf test case, and some are not compatible with clang LTO
  (they assume binary in the .o, not bitcode)
- force llvm-ar instead of ar, as ar is not aware of .o files generated
  by clang -flto






run autoconf (GH-9411)
2018-09-19T06:49:05+00:00

Benjamin Peterson
benjamin@python.org

2018-09-19T06:49:05+00:00

b3b8cb419e496629873fa7dda82a01863f58617a

Follow up to 2a9c3805ddedf282881ef7811a561c70b74f80b1 (bpo-34585).




Follow up to 2a9c3805ddedf282881ef7811a561c70b74f80b1 (bpo-34585).






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-32430: Rename Modules/Setup.dist to Modules/Setup (GH-8229)
2018-07-16T17:03:03+00:00

Antoine Pitrou
pitrou@free.fr

2018-07-16T17:03:03+00:00

961d54c5c1916c09883ebcf7191babc969e5a5cf

bpo-32430: Rename Modules/Setup.dist to Modules/Setup

Remove the necessity to copy the former manually to the latter when updating the local source tree.




bpo-32430: Rename Modules/Setup.dist to Modules/Setup

Remove the necessity to copy the former manually to the latter when updating the local source tree.