From da320a9bb75f546eeecc01377d63d6fd4237b00c Mon Sep 17 00:00:00 2001 From: Jean-Christophe Fillion-Robin Date: Mon, 31 Jul 2017 14:50:48 -0400 Subject: [PATCH 01/11] Add Readme and License --- LICENSE_Apache_20 | 192 ++++++++++++++++++++++++++++++++++++++++++++++ README.rst | 49 ++++++++++++ 2 files changed, 241 insertions(+) create mode 100644 LICENSE_Apache_20 create mode 100644 README.rst diff --git a/LICENSE_Apache_20 b/LICENSE_Apache_20 new file mode 100644 index 00000000000000..10efdfbd52b67d --- /dev/null +++ b/LICENSE_Apache_20 @@ -0,0 +1,192 @@ +Apache License +Version 2.0, January 2004 +http://www.apache.org/licenses/ + +TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + +1. Definitions. + +"License" shall mean the terms and conditions for use, reproduction, and +distribution as defined by Sections 1 through 9 of this document. + +"Licensor" shall mean the copyright owner or entity authorized by the copyright +owner that is granting the License. + +"Legal Entity" shall mean the union of the acting entity and all other entities +that control, are controlled by, or are under common control with that entity. +For the purposes of this definition, "control" means (i) the power, direct or +indirect, to cause the direction or management of such entity, whether by +contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the +outstanding shares, or (iii) beneficial ownership of such entity. + +"You" (or "Your") shall mean an individual or Legal Entity exercising +permissions granted by this License. + +"Source" form shall mean the preferred form for making modifications, including +but not limited to software source code, documentation source, and configuration +files. + +"Object" form shall mean any form resulting from mechanical transformation or +translation of a Source form, including but not limited to compiled object code, +generated documentation, and conversions to other media types. + +"Work" shall mean the work of authorship, whether in Source or Object form, made +available under the License, as indicated by a copyright notice that is included +in or attached to the work (an example is provided in the Appendix below). + +"Derivative Works" shall mean any work, whether in Source or Object form, that +is based on (or derived from) the Work and for which the editorial revisions, +annotations, elaborations, or other modifications represent, as a whole, an +original work of authorship. For the purposes of this License, Derivative Works +shall not include works that remain separable from, or merely link (or bind by +name) to the interfaces of, the Work and Derivative Works thereof. + +"Contribution" shall mean any work of authorship, including the original version +of the Work and any modifications or additions to that Work or Derivative Works +thereof, that is intentionally submitted to Licensor for inclusion in the Work +by the copyright owner or by an individual or Legal Entity authorized to submit +on behalf of the copyright owner. For the purposes of this definition, +"submitted" means any form of electronic, verbal, or written communication sent +to the Licensor or its representatives, including but not limited to +communication on electronic mailing lists, source code control systems, and +issue tracking systems that are managed by, or on behalf of, the Licensor for +the purpose of discussing and improving the Work, but excluding communication +that is conspicuously marked or otherwise designated in writing by the copyright +owner as "Not a Contribution." + +"Contributor" shall mean Licensor and any individual or Legal Entity on behalf +of whom a Contribution has been received by Licensor and subsequently +incorporated within the Work. + +2. Grant of Copyright License. + +Subject to the terms and conditions of this License, each Contributor hereby +grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, +irrevocable copyright license to reproduce, prepare Derivative Works of, +publicly display, publicly perform, sublicense, and distribute the Work and such +Derivative Works in Source or Object form. + +3. Grant of Patent License. + +Subject to the terms and conditions of this License, each Contributor hereby +grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, +irrevocable (except as stated in this section) patent license to make, have +made, use, offer to sell, sell, import, and otherwise transfer the Work, where +such license applies only to those patent claims licensable by such Contributor +that are necessarily infringed by their Contribution(s) alone or by combination +of their Contribution(s) with the Work to which such Contribution(s) was +submitted. If You institute patent litigation against any entity (including a +cross-claim or counterclaim in a lawsuit) alleging that the Work or a +Contribution incorporated within the Work constitutes direct or contributory +patent infringement, then any patent licenses granted to You under this License +for that Work shall terminate as of the date such litigation is filed. + +4. Redistribution. + +You may reproduce and distribute copies of the Work or Derivative Works thereof +in any medium, with or without modifications, and in Source or Object form, +provided that You meet the following conditions: + +You must give any other recipients of the Work or Derivative Works a copy of +this License; and +You must cause any modified files to carry prominent notices stating that You +changed the files; and +You must retain, in the Source form of any Derivative Works that You distribute, +all copyright, patent, trademark, and attribution notices from the Source form +of the Work, excluding those notices that do not pertain to any part of the +Derivative Works; and +If the Work includes a "NOTICE" text file as part of its distribution, then any +Derivative Works that You distribute must include a readable copy of the +attribution notices contained within such NOTICE file, excluding those notices +that do not pertain to any part of the Derivative Works, in at least one of the +following places: within a NOTICE text file distributed as part of the +Derivative Works; within the Source form or documentation, if provided along +with the Derivative Works; or, within a display generated by the Derivative +Works, if and wherever such third-party notices normally appear. The contents of +the NOTICE file are for informational purposes only and do not modify the +License. You may add Your own attribution notices within Derivative Works that +You distribute, alongside or as an addendum to the NOTICE text from the Work, +provided that such additional attribution notices cannot be construed as +modifying the License. +You may add Your own copyright statement to Your modifications and may provide +additional or different license terms and conditions for use, reproduction, or +distribution of Your modifications, or for any such Derivative Works as a whole, +provided Your use, reproduction, and distribution of the Work otherwise complies +with the conditions stated in this License. + +5. Submission of Contributions. + +Unless You explicitly state otherwise, any Contribution intentionally submitted +for inclusion in the Work by You to the Licensor shall be under the terms and +conditions of this License, without any additional terms or conditions. +Notwithstanding the above, nothing herein shall supersede or modify the terms of +any separate license agreement you may have executed with Licensor regarding +such Contributions. + +6. Trademarks. + +This License does not grant permission to use the trade names, trademarks, +service marks, or product names of the Licensor, except as required for +reasonable and customary use in describing the origin of the Work and +reproducing the content of the NOTICE file. + +7. Disclaimer of Warranty. + +Unless required by applicable law or agreed to in writing, Licensor provides the +Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, +including, without limitation, any warranties or conditions of TITLE, +NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are +solely responsible for determining the appropriateness of using or +redistributing the Work and assume any risks associated with Your exercise of +permissions under this License. + +8. Limitation of Liability. + +In no event and under no legal theory, whether in tort (including negligence), +contract, or otherwise, unless required by applicable law (such as deliberate +and grossly negligent acts) or agreed to in writing, shall any Contributor be +liable to You for damages, including any direct, indirect, special, incidental, +or consequential damages of any character arising as a result of this License or +out of the use or inability to use the Work (including but not limited to +damages for loss of goodwill, work stoppage, computer failure or malfunction, or +any and all other commercial damages or losses), even if such Contributor has +been advised of the possibility of such damages. + +9. Accepting Warranty or Additional Liability. + +While redistributing the Work or Derivative Works thereof, You may choose to +offer, and charge a fee for, acceptance of support, warranty, indemnity, or +other liability obligations and/or rights consistent with this License. However, +in accepting such obligations, You may act only on Your own behalf and on Your +sole responsibility, not on behalf of any other Contributor, and only if You +agree to indemnify, defend, and hold each Contributor harmless for any liability +incurred by, or claims asserted against, such Contributor by reason of your +accepting any such warranty or additional liability. + +END OF TERMS AND CONDITIONS + +APPENDIX: How to apply the Apache License to your work + +To apply the Apache License to your work, attach the following boilerplate +notice, with the fields enclosed by brackets "[]" replaced with your own +identifying information. (Don't include the brackets!) The text should be +enclosed in the appropriate comment syntax for the file format. We also +recommend that a file or class name and description of purpose be included on +the same "printed page" as the copyright notice for easier identification within +third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + diff --git a/README.rst b/README.rst new file mode 100644 index 00000000000000..08bd87afc7bff4 --- /dev/null +++ b/README.rst @@ -0,0 +1,49 @@ +CPython Patches +=============== + +This project is an unofficial fork of `CPython `_ sources used as +staging area to maintain and test CPython patches. + +Fixes and improvements to CPython should first be contributed upstream. The +`Python Developer’s Guide `_ is a great +resource to guide you through the process. + +That said, there are few scenarios where maintaining CPython patches is relevant: + +* When there is a need for a staging area for patches waiting to be integrated + upstream. Doing so avoid each project to maintain their own set of patches. + +* When the proposed patches are specific to a system not officially supported + (e.g Android, Emscripten, ...). + +* When generalizing proposed patches is definitively not feasible given the + time and resources. + +* When patches fix an older version of CPython (e.g. 2.7) so that it can + be compiled using newer compiler (e.g VS2015). + + +Available branches +------------------ + +* `2.7.13-patches `_: + + * Support for VS2010 and VS2015 + + +License +------- + +All software is licensed under the Apache 2.0 License. +See `LICENSE_Apache_20 `_ file for details. + +Why Apache 2.0 License? +....................... + +From the python.org wiki, the answer to the question `What if I want to +contribute my code to the PSF +`_ +mentions that if code is going to end up in Python or the standard library, +the PSF will require you to license code under "Academic Free License" or +"Apache License 2.0". + From 824f39db630ca43dc249fb1dce66efb023d30090 Mon Sep 17 00:00:00 2001 From: Jean-Christophe Fillion-Robin Date: Mon, 6 Nov 2017 19:40:21 -0500 Subject: [PATCH 02/11] Reference 3.5.3 branches --- README.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.rst b/README.rst index 08bd87afc7bff4..ca49e6cac72b81 100644 --- a/README.rst +++ b/README.rst @@ -30,6 +30,15 @@ Available branches * Support for VS2010 and VS2015 +* `3.5.3-patches `_: + + * Rename header files found in ``Modules/_decimal/libmpdec`` directory to avoid conflicts with system headers + of the same name (``io.h`` and ``memory.h``). This script was originally used to update the sources: https://gist.github.com/jcfr/e166c0f3fd823de2586b1101f9c67947 + + * Prevent duplicated ``OverlappedType`` symbols with built-in extension on Windows. + + * Export inlined functions to support extension built-in on Windows. + License ------- From 105420569ddc307d0138d71c6f423ad516d147e8 Mon Sep 17 00:00:00 2001 From: Jean-Christophe Fillion-Robin Date: Mon, 6 Nov 2017 21:46:39 -0500 Subject: [PATCH 03/11] Reference 3.6.2 branches --- README.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.rst b/README.rst index ca49e6cac72b81..4ebdc87e8179e3 100644 --- a/README.rst +++ b/README.rst @@ -39,6 +39,15 @@ Available branches * Export inlined functions to support extension built-in on Windows. +* `3.6.2-patches `_: + + * Rename header files found in ``Modules/_decimal/libmpdec`` directory to avoid conflicts with system headers + of the same name (``io.h``). This script was originally used to update the sources: https://gist.github.com/jcfr/e166c0f3fd823de2586b1101f9c67947 + + * Prevent duplicated ``OverlappedType`` symbols with built-in extension on Windows. + + * Export inlined functions to support extension built-in on Windows. + License ------- From c7d2855932dc42c486f959878c8008be4fc147a0 Mon Sep 17 00:00:00 2001 From: Jean-Christophe Fillion-Robin Date: Sun, 18 Mar 2018 18:52:27 -0400 Subject: [PATCH 04/11] Reference 2.7.3 to 2.7.6 branches --- README.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.rst b/README.rst index 4ebdc87e8179e3..7218fecb95810f 100644 --- a/README.rst +++ b/README.rst @@ -26,6 +26,14 @@ That said, there are few scenarios where maintaining CPython patches is relevant Available branches ------------------ +* `2.7.3-patches `_: + + * Fix build with GNU readline >= 6.3. - Apply to 2.7.3 and 2.7.4 + +* `2.7.5-patches `_: + + * Fix build with GNU readline >= 6.3. - Apply to 2.7.5 and 2.7.6 + * `2.7.13-patches `_: * Support for VS2010 and VS2015 From 570ebc12542f2ecb008cb005d86089ec442c6c6a Mon Sep 17 00:00:00 2001 From: Jean-Christophe Fillion-Robin Date: Fri, 12 Apr 2019 15:59:53 -0400 Subject: [PATCH 05/11] README: Clarify how are applied 2.7.13-patches --- README.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.rst b/README.rst index 7218fecb95810f..d7d9e9d42060ce 100644 --- a/README.rst +++ b/README.rst @@ -36,7 +36,7 @@ Available branches * `2.7.13-patches `_: - * Support for VS2010 and VS2015 + * Support for VS2010 and VS2015. - Apply to 2.7.14 and 2.7.15. See `PythonApplyPatches.cmake `_ * `3.5.3-patches `_: From af909a515473d8d571af261494335f60799a02a6 Mon Sep 17 00:00:00 2001 From: Jean-Christophe Fillion-Robin Date: Fri, 12 Apr 2019 16:04:29 -0400 Subject: [PATCH 06/11] README: Clarify how are applied 3.5 and 3.6 patches --- README.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.rst b/README.rst index d7d9e9d42060ce..058222db4b2a7e 100644 --- a/README.rst +++ b/README.rst @@ -41,20 +41,20 @@ Available branches * `3.5.3-patches `_: * Rename header files found in ``Modules/_decimal/libmpdec`` directory to avoid conflicts with system headers - of the same name (``io.h`` and ``memory.h``). This script was originally used to update the sources: https://gist.github.com/jcfr/e166c0f3fd823de2586b1101f9c67947 + of the same name (``io.h`` and ``memory.h``). This script was originally used to update the sources: https://gist.github.com/jcfr/e166c0f3fd823de2586b1101f9c67947. - Apply to 3.5.x - * Prevent duplicated ``OverlappedType`` symbols with built-in extension on Windows. + * Prevent duplicated ``OverlappedType`` symbols with built-in extension on Windows. - Apply to 3.5.x - * Export inlined functions to support extension built-in on Windows. + * Export inlined functions to support extension built-in on Windows. - Apply to 3.5.x * `3.6.2-patches `_: * Rename header files found in ``Modules/_decimal/libmpdec`` directory to avoid conflicts with system headers - of the same name (``io.h``). This script was originally used to update the sources: https://gist.github.com/jcfr/e166c0f3fd823de2586b1101f9c67947 + of the same name (``io.h``). This script was originally used to update the sources: https://gist.github.com/jcfr/e166c0f3fd823de2586b1101f9c67947. - Apply to 3.6.x - * Prevent duplicated ``OverlappedType`` symbols with built-in extension on Windows. + * Prevent duplicated ``OverlappedType`` symbols with built-in extension on Windows. - Apply to 3.6.x - * Export inlined functions to support extension built-in on Windows. + * Export inlined functions to support extension built-in on Windows. - Apply to 3.6.x License From b5241d128dbc9196b62ff2ca24da88d01ce09bc0 Mon Sep 17 00:00:00 2001 From: Jean-Christophe Fillion-Robin Date: Mon, 27 Dec 2021 05:33:23 -0500 Subject: [PATCH 07/11] README: Reference 2.7.15-patches branch, mention patches for 2.7.11 and 2.7.12 --- README.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.rst b/README.rst index 058222db4b2a7e..4d0880840be13c 100644 --- a/README.rst +++ b/README.rst @@ -36,7 +36,11 @@ Available branches * `2.7.13-patches `_: - * Support for VS2010 and VS2015. - Apply to 2.7.14 and 2.7.15. See `PythonApplyPatches.cmake `_ + * Support for VS2010 and VS2015. - Apply to 2.7.11, 2.7.12 and 2.7.14. See `PythonApplyPatches.cmake `_ + +* `2.7.15-patches `_: + + * Support for VS2010 and VS2015. * `3.5.3-patches `_: From 585d405ea92eed79e43503b0ead680520520d9db Mon Sep 17 00:00:00 2001 From: Jean-Christophe Fillion-Robin Date: Tue, 18 Jan 2022 04:30:58 -0500 Subject: [PATCH 08/11] README: Mention 2.7.x patches related to MinGW support --- README.rst | 25 ++++++++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) diff --git a/README.rst b/README.rst index 4d0880840be13c..99d264776c1e92 100644 --- a/README.rst +++ b/README.rst @@ -28,19 +28,29 @@ Available branches * `2.7.3-patches `_: - * Fix build with GNU readline >= 6.3. - Apply to 2.7.3 and 2.7.4 + * Fix build with GNU readline >= 6.3. + * Support for MinGW (building ``socket`` and ``ctypes`` modules is not supported). + + *Apply to 2.7.3 and 2.7.4* * `2.7.5-patches `_: - * Fix build with GNU readline >= 6.3. - Apply to 2.7.5 and 2.7.6 + * Fix build with GNU readline >= 6.3. + * Support for MinGW (building ``socket`` and ``ctypes`` modules is not supported). + + *Apply to 2.7.5 and 2.7.6* * `2.7.13-patches `_: - * Support for VS2010 and VS2015. - Apply to 2.7.11, 2.7.12 and 2.7.14. See `PythonApplyPatches.cmake `_ + * Support for VS2010 and VS2015. + * Support for MinGW (building ``socket`` and ``ctypes`` modules is not supported). + + *Apply to 2.7.11, 2.7.12 and 2.7.14* * `2.7.15-patches `_: * Support for VS2010 and VS2015. + * Support for MinGW (building ``socket`` and ``ctypes`` modules is not supported). * `3.5.3-patches `_: @@ -77,3 +87,12 @@ mentions that if code is going to end up in Python or the standard library, the PSF will require you to license code under "Academic Free License" or "Apache License 2.0". +How are the patches applied ? +............................. + +Patches associated with a given branches are generated using the ``git format-patch`` command and +added to the relevant sub-directories of the ``python-cmake-buildsystem`` project. These are then +automatically applied are configuration time using the `PythonApplyPatches `_ CMake module. + +Read more details at `python-cmake-buildsystem/patches/README.rst `_. + From 8c5204c1d7b6b6c9169ab24214eccefb6f38ef7d Mon Sep 17 00:00:00 2001 From: Jean-Christophe Fillion-Robin Date: Mon, 2 Jun 2025 12:20:39 -0400 Subject: [PATCH 09/11] README: Order branch descriptions from latest to oldest --- README.rst | 46 +++++++++++++++++++++++----------------------- 1 file changed, 23 insertions(+), 23 deletions(-) diff --git a/README.rst b/README.rst index 99d264776c1e92..2de952d0d23d86 100644 --- a/README.rst +++ b/README.rst @@ -26,49 +26,49 @@ That said, there are few scenarios where maintaining CPython patches is relevant Available branches ------------------ -* `2.7.3-patches `_: +* `3.6.2-patches `_: - * Fix build with GNU readline >= 6.3. - * Support for MinGW (building ``socket`` and ``ctypes`` modules is not supported). + * Rename header files found in ``Modules/_decimal/libmpdec`` directory to avoid conflicts with system headers + of the same name (``io.h``). This script was originally used to update the sources: https://gist.github.com/jcfr/e166c0f3fd823de2586b1101f9c67947. - Apply to 3.6.x - *Apply to 2.7.3 and 2.7.4* + * Prevent duplicated ``OverlappedType`` symbols with built-in extension on Windows. - Apply to 3.6.x -* `2.7.5-patches `_: + * Export inlined functions to support extension built-in on Windows. - Apply to 3.6.x + +* `3.5.3-patches `_: - * Fix build with GNU readline >= 6.3. - * Support for MinGW (building ``socket`` and ``ctypes`` modules is not supported). + * Rename header files found in ``Modules/_decimal/libmpdec`` directory to avoid conflicts with system headers + of the same name (``io.h`` and ``memory.h``). This script was originally used to update the sources: https://gist.github.com/jcfr/e166c0f3fd823de2586b1101f9c67947. - Apply to 3.5.x - *Apply to 2.7.5 and 2.7.6* + * Prevent duplicated ``OverlappedType`` symbols with built-in extension on Windows. - Apply to 3.5.x -* `2.7.13-patches `_: + * Export inlined functions to support extension built-in on Windows. - Apply to 3.5.x + +* `2.7.15-patches `_: * Support for VS2010 and VS2015. * Support for MinGW (building ``socket`` and ``ctypes`` modules is not supported). - *Apply to 2.7.11, 2.7.12 and 2.7.14* - -* `2.7.15-patches `_: +* `2.7.13-patches `_: * Support for VS2010 and VS2015. * Support for MinGW (building ``socket`` and ``ctypes`` modules is not supported). -* `3.5.3-patches `_: - - * Rename header files found in ``Modules/_decimal/libmpdec`` directory to avoid conflicts with system headers - of the same name (``io.h`` and ``memory.h``). This script was originally used to update the sources: https://gist.github.com/jcfr/e166c0f3fd823de2586b1101f9c67947. - Apply to 3.5.x + *Apply to 2.7.11, 2.7.12 and 2.7.14* - * Prevent duplicated ``OverlappedType`` symbols with built-in extension on Windows. - Apply to 3.5.x +* `2.7.5-patches `_: - * Export inlined functions to support extension built-in on Windows. - Apply to 3.5.x + * Fix build with GNU readline >= 6.3. + * Support for MinGW (building ``socket`` and ``ctypes`` modules is not supported). -* `3.6.2-patches `_: + *Apply to 2.7.5 and 2.7.6* - * Rename header files found in ``Modules/_decimal/libmpdec`` directory to avoid conflicts with system headers - of the same name (``io.h``). This script was originally used to update the sources: https://gist.github.com/jcfr/e166c0f3fd823de2586b1101f9c67947. - Apply to 3.6.x +* `2.7.3-patches `_: - * Prevent duplicated ``OverlappedType`` symbols with built-in extension on Windows. - Apply to 3.6.x + * Fix build with GNU readline >= 6.3. + * Support for MinGW (building ``socket`` and ``ctypes`` modules is not supported). - * Export inlined functions to support extension built-in on Windows. - Apply to 3.6.x + *Apply to 2.7.3 and 2.7.4* License From b99dbd0d70c053bb63496eb82a2f8d9b26e9744e Mon Sep 17 00:00:00 2001 From: Jean-Christophe Fillion-Robin Date: Mon, 2 Jun 2025 12:30:12 -0400 Subject: [PATCH 10/11] README: Update `3.6.2-patches` description --- README.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.rst b/README.rst index 2de952d0d23d86..e653739b0dfd0b 100644 --- a/README.rst +++ b/README.rst @@ -28,6 +28,8 @@ Available branches * `3.6.2-patches `_: + * Fix Windows build of Python for latest WinSDK. - Apply to 3.6.x + * Rename header files found in ``Modules/_decimal/libmpdec`` directory to avoid conflicts with system headers of the same name (``io.h``). This script was originally used to update the sources: https://gist.github.com/jcfr/e166c0f3fd823de2586b1101f9c67947. - Apply to 3.6.x From 3317e1c64fff03da49324552a05991fb299decba Mon Sep 17 00:00:00 2001 From: Jean-Christophe Fillion-Robin Date: Mon, 2 Jun 2025 12:30:47 -0400 Subject: [PATCH 11/11] README: Add `3.6.15`, `3.11.0` and `3.12.0` descriptions --- README.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/README.rst b/README.rst index e653739b0dfd0b..5a3108e7236bdb 100644 --- a/README.rst +++ b/README.rst @@ -26,6 +26,24 @@ That said, there are few scenarios where maintaining CPython patches is relevant Available branches ------------------ +* `3.12.0-patches `_: + + * _bootstrap_python: Fix execution on windows disabling site import + * getpath: Update build directory assumptions based on python-cmake-buildsystem + + *Apply to 3.12.x* + +* `3.11.0-patches `_: + + * _bootstrap_python: Fix execution on windows disabling site import + * getpath: Update build directory assumptions based on python-cmake-buildsystem + + *Apply to 3.11.x* + +* `3.6.15-patches `_: + + * bpo-35519: Rename ``test.bisect`` to ``test.bisect_cmd``. - Apply to 3.6.15 + * `3.6.2-patches `_: * Fix Windows build of Python for latest WinSDK. - Apply to 3.6.x