delta/cpython-git.git, branch v3.7.14 github.com: python/cpython.git gh-91423: Remove bugs.python.org from bugs.rst (GH-91425) 2022-09-06T07:11:33+00:00 roy reznik royreznik@gmail.com 2022-04-11T15:10:34+00:00 e1ebdc52b8bd82a928398b0a75149552a723389a Co-authored-by: Inada Naoki <songofacandy@gmail.com> Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com> 
Co-authored-by: Inada Naoki <songofacandy@gmail.com>
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
3.7.14 2022-09-06T06:57:17+00:00 Ned Deily nad@python.org 2022-09-06T06:57:17+00:00 61e371aafb9a72a1382f6e9df6dd54f8a2107f95 






Move doc build dependencies to Doc/requirements.txt (GH-96607)
2022-09-06T06:34:50+00:00

Ned Deily
nad@python.org

2022-09-06T06:34:50+00:00

8feefc281f03c0f1af3422a8f0febb68edb145f2

This makes 3.7 doc builds similar to later releases,
simplifying build tooling.




This makes 3.7 doc builds similar to later releases,
simplifying build tooling.






[3.7] gh-95778: CVE-2020-10735: Prevent DoS by very large int() (GH-96504)
2022-09-06T05:24:36+00:00

Gregory P. Smith
greg@krypto.org

2022-09-06T05:24:36+00:00

15ec1afd4fcd2da1e2d2b256c562fb42d8d886a2

Converting between `int` and `str` in bases other than 2
(binary), 4, 8 (octal), 16 (hexadecimal), or 32 such as base 10 (decimal) now
raises a `ValueError` if the number of digits in string form is above a
limit to avoid potential denial of service attacks due to the algorithmic
complexity. This is a mitigation for CVE-2020-10735
(https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10735).

This new limit can be configured or disabled by environment variable, command
line flag, or :mod:`sys` APIs. See the `Integer String Conversion Length
Limitation` documentation.  The default limit is 4300
digits in string form.

Patch by Gregory P. Smith [Google] and Christian Heimes [Red Hat] with feedback
from Victor Stinner, Thomas Wouters, Steve Dower, Ned Deily, and Mark Dickinson.




Converting between `int` and `str` in bases other than 2
(binary), 4, 8 (octal), 16 (hexadecimal), or 32 such as base 10 (decimal) now
raises a `ValueError` if the number of digits in string form is above a
limit to avoid potential denial of service attacks due to the algorithmic
complexity. This is a mitigation for CVE-2020-10735
(https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10735).

This new limit can be configured or disabled by environment variable, command
line flag, or :mod:`sys` APIs. See the `Integer String Conversion Length
Limitation` documentation.  The default limit is 4300
digits in string form.

Patch by Gregory P. Smith [Google] and Christian Heimes [Red Hat] with feedback
from Victor Stinner, Thomas Wouters, Steve Dower, Ned Deily, and Mark Dickinson.






bpo-35036: Remove empty log line in the suspicious.py tool (GH-10024) (GH-96498)
2022-09-02T03:53:11+00:00

Gregory P. Smith
greg@krypto.org

2022-09-02T03:53:11+00:00

d5fe9951fe6e69e9175eca24170a220747ec9047

Previous to commit ee171a2 the logline was working because of self.info() (now
deprecated) defaults to an empty message.

Co-authored-by: Xtreak <tirkarthi@users.noreply.github.com>




Previous to commit ee171a2 the logline was working because of self.info() (now
deprecated) defaults to an empty message.

Co-authored-by: Xtreak <tirkarthi@users.noreply.github.com>






[3.7] fix CI on macOS due to infrastructure changes (GH-96493)
2022-09-02T03:46:48+00:00

Gregory P. Smith
greg@krypto.org

2022-09-02T03:46:48+00:00

6fde29377fd57fea13a54dd847b7cf171c2df6d1

* Add ABI and generated files checks to CI.

This includes checking in an initial Abigail ABI definition for 3.7.

* Backport ctypes test_macholib fix from b29d0a5a7811418c0a1082ca188fd4850185e290.

This is required for the 3.7 tree to pass on modern macOS.

* annotate test_bad_password @requires_zlib.

I don't know why, but macOS in 3.7 CI is failing to build the zlib
module these days so it's exposing this test that didn't have the
proper `@requires_zlib` annotation.

Getting it to build with zlib and other things that are now wrongly
"missing" in the 3.7 CI setup would be nice, but probably involves
invasive backporting of parts of
https://github.com/python/cpython/commit/b29d0a5a7811418c0a1082ca188fd4850185e290
by a macOS domain expert.

Not worth it.

* disable MachOTest.test_find unless macOS 11+ support is backported.

This test also appears to require changes to
Lib/ctypes/macholib/dyld.py to work in the existing macOS CI config.
I'm just skipping it, backporting that would be a feature.
Not going to happen in 3.7.

There may be a way to configure macOS CI to use an older macOS and
toolchain instead as an alternate option.  Someone else can figure
that out if so.  This branch only lives for another 9 months per
https://peps.python.org/pep-0537/

* LOL at my typo

Co-authored-by: Ned Deily <nad@python.org>




* Add ABI and generated files checks to CI.

This includes checking in an initial Abigail ABI definition for 3.7.

* Backport ctypes test_macholib fix from b29d0a5a7811418c0a1082ca188fd4850185e290.

This is required for the 3.7 tree to pass on modern macOS.

* annotate test_bad_password @requires_zlib.

I don't know why, but macOS in 3.7 CI is failing to build the zlib
module these days so it's exposing this test that didn't have the
proper `@requires_zlib` annotation.

Getting it to build with zlib and other things that are now wrongly
"missing" in the 3.7 CI setup would be nice, but probably involves
invasive backporting of parts of
https://github.com/python/cpython/commit/b29d0a5a7811418c0a1082ca188fd4850185e290
by a macOS domain expert.

Not worth it.

* disable MachOTest.test_find unless macOS 11+ support is backported.

This test also appears to require changes to
Lib/ctypes/macholib/dyld.py to work in the existing macOS CI config.
I'm just skipping it, backporting that would be a feature.
Not going to happen in 3.7.

There may be a way to configure macOS CI to use an older macOS and
toolchain instead as an alternate option.  Someone else can figure
that out if so.  This branch only lives for another 9 months per
https://peps.python.org/pep-0537/

* LOL at my typo

Co-authored-by: Ned Deily <nad@python.org>






bpo-40548: Fix "Check for source changes (pull_request)" GH Action job (GH-21806) (GH-92342)
2022-09-02T03:28:11+00:00

Miss Islington (bot)
31488909+miss-islington@users.noreply.github.com

2022-09-02T03:28:11+00:00

9d58933c20cd49c9a78d54483f27add6cb18138d

On Git 2.28, "git diff master..." (3 dots) no longer works when
"fetch --depth=1" is used, whereas it works on Git 2.26.

Replace "..." (3 dots) with ".." (2 dots) in the "git diff" command
computing the list of modified files between the base branch and the
PR branch.
(cherry picked from commit eaa551702d80fd67219c48ee6a13ffb571ca360b)

Co-authored-by: Victor Stinner <vstinner@python.org>




On Git 2.28, "git diff master..." (3 dots) no longer works when
"fetch --depth=1" is used, whereas it works on Git 2.26.

Replace "..." (3 dots) with ".." (2 dots) in the "git diff" command
computing the list of modified files between the base branch and the
PR branch.
(cherry picked from commit eaa551702d80fd67219c48ee6a13ffb571ca360b)

Co-authored-by: Victor Stinner <vstinner@python.org>






[3.7] Fix the Windows CI config. (GH-96490)
2022-09-01T22:17:14+00:00

Gregory P. Smith
greg@krypto.org

2022-09-01T22:17:14+00:00

9da350265f4065d6381148fb3f8c79d1f058cf6d

* Add ABI and generated files checks to CI.
* Fix the Windows CI config.

This matches what 3.8 did in 899eb4167264a17ba703677814d69d4f7dcaea41.




* Add ABI and generated files checks to CI.
* Fix the Windows CI config.

This matches what 3.8 did in 899eb4167264a17ba703677814d69d4f7dcaea41.






bpo-41306: Allow scale value to not be rounded (GH-21715) (GH-96484)
2022-09-01T19:23:27+00:00

Miss Islington (bot)
31488909+miss-islington@users.noreply.github.com

2022-09-01T19:23:27+00:00

bb8e49b4203fc1f2df554b452dbd3926102b18ee

This fixes the test failure with Tk 6.8.10 which is caused by changes to how Tk rounds the `from`, `to` and `tickinterval` arguments. This PR uses `noconv` if the patchlevel is greater than or equal to 8.6.10 (credit to Serhiy for this idea as it is much simpler than what I previously proposed).

Going into more detail for those who want it, the Tk change was made in [commit 591f68c](https://github.com/tcltk/tk/commit/591f68cb382525b72664c6fecaab87742b6cc87a) and means that the arguments listed above are rounded relative to the value of `from`. However, when rounding the `from` argument ([line 623](https://github.com/tcltk/tk/blob/591f68cb382525b72664c6fecaab87742b6cc87a/generic/tkScale.cGH-L623)), it is rounded relative to itself (i.e. rounding `0`) and therefore the assigned value for `from` is always what is given (no matter what values of `from` and `resolution`).

Automerge-Triggered-By: @pablogsal
(cherry picked from commit aecf036738a404371303e770f4ce4fd9f7d43de7)

Co-authored-by: E-Paine <63801254+E-Paine@users.noreply.github.com>




This fixes the test failure with Tk 6.8.10 which is caused by changes to how Tk rounds the `from`, `to` and `tickinterval` arguments. This PR uses `noconv` if the patchlevel is greater than or equal to 8.6.10 (credit to Serhiy for this idea as it is much simpler than what I previously proposed).

Going into more detail for those who want it, the Tk change was made in [commit 591f68c](https://github.com/tcltk/tk/commit/591f68cb382525b72664c6fecaab87742b6cc87a) and means that the arguments listed above are rounded relative to the value of `from`. However, when rounding the `from` argument ([line 623](https://github.com/tcltk/tk/blob/591f68cb382525b72664c6fecaab87742b6cc87a/generic/tkScale.cGH-L623)), it is rounded relative to itself (i.e. rounding `0`) and therefore the assigned value for `from` is always what is given (no matter what values of `from` and `resolution`).

Automerge-Triggered-By: @pablogsal
(cherry picked from commit aecf036738a404371303e770f4ce4fd9f7d43de7)

Co-authored-by: E-Paine <63801254+E-Paine@users.noreply.github.com>






[3.7] gh-94208: Add more TLS version/protocol checks for FreeBSD (GH-94347) (GH-95314)
2022-07-27T21:45:05+00:00

Łukasz Langa
lukasz@langa.pl

2022-07-27T21:45:05+00:00

c19983125a42a4b4958b11a26ab5e03752c956fc

Three test cases were failing on FreeBSD with latest OpenSSL.
(cherry picked from commit 1bc86c26253befa006c0f52eebb6ed633c7d1e5c)

Co-authored-by: Christian Heimes <christian@python.org>




Three test cases were failing on FreeBSD with latest OpenSSL.
(cherry picked from commit 1bc86c26253befa006c0f52eebb6ed633c7d1e5c)

Co-authored-by: Christian Heimes <christian@python.org>