python-committers December 2018

python-committers@python.org

16 participants
12 discussions

GitHub: remove the "needs backport to 3.5" label?

by Victor Stinner

Hi, Python 3.5 entered security fix only mode. Should we now remove the "needs backport to 3.5" label? Other security only branches don't have this label neither (3.3 and 3.4). Victor

2 years, 5 months

Re: [python-committers] [Python-Dev] 3.7.2rc1 and 3.6.8rc1 cutoffs ahead, last 3.6.x bugfix release!

by Victor Stinner

Hi, I am working in the Red Hat "Python-maint" team which is maintaining Python 3.6 as the main Python interpreter in RHEL 8, which will likely be supported for at least 10 years. And we have been supporting Python 2.7 in RHEL 7. So obviously, being able to benefit of the upstream effort and infra to have a Python 3.6 Long Time Support (LTS) would help us :-) The question is more who else would benefit from that and is it worth it? I don't want Python upstream to pay the price of the maintenance burden of RHEL 8 lifecycle. For example, supporting a version means to have a working CI (Travis CI, AppVeyor, VSTS, buildbots). I would suggest to only support a very few platforms for the LTS. I propose to restrict to Linux. It doesn't mean to break other platforms on purpose, just to restrict CI to the bare minimum. If Microsoft is interested, we can also support Windows as well. RHEL 7 is based on Python 2.7.5 which has been released in 2013 (5 years ago) and there are 150 patches on top of it: it means that around 30 patches are added per year. I would suggest to have a very strict policy on which changes are backported into 3.6: only the most critical bugfixes, but all security fixes obviously. If we extend Python 3.6 lifetime, do we need a new release manager when the initial lifetime (usually 5 years) ends? Benjamin Peterson accepted to be the Python 2.7 release manager for 10 years (instead of 5 years initially). We could ask Ned Deily about Python 3.6 LTS :-) We would need a group of people reviewing individual 3.6 pull requests to decide to pick them or not. I would volunteer to review these PRs and merge them. The idea isn't new, Nick Coghlan proposed a "ELPython" last year: https://github.com/elpython/elpython-meta The Linux kernel also have multiple LTS kernel which are supported longer than usual releases: they are now supported for 6 years. See "Longterm" at: https://www.kernel.org/category/releases.html Victor -- Night gathers, and now my watch begins. It shall not end until my death.

3 years

[RELEASE] Python 3.7.2 and 3.6.8 are now available

by Ned Deily

https://blog.python.org/2018/12/python-372-and-368-are-now-available.html Python 3.7.2 and 3.6.8 are now available. Python 3.7.2 is the next maintenance release of Python 3.7, the latest feature release of Python. You can find Python 3.7.2 here: https://www.python.org/downloads/release/python-372/ See the What’s New In Python 3.7 document for more information about the many new features and optimizations included in the 3.7 series. Detailed information about the changes made in 3.7.2 can be found in its change log. We are also happy to announce the availability of Python 3.6.8: https://www.python.org/downloads/release/python-368/ Python 3.6.8 is planned to be the last bugfix release of Python 3.6. Per our support policy, we plan to provide security fixes for Python 3.6 as needed through 2021, five years following its initial release. Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. https://docs.python.org/3.7/whatsnew/3.7.html https://docs.python.org/3.7/whatsnew/changelog.html#python-3-7-2-final https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-8-final https://www.python.org/psf/ -- Ned Deily nad(a)python.org -- []

3 years

Poll to choose a voting timeline for the steering council

by Brett Cannon

I didn't put a close date on the poll, but obviously the sooner we can resolve this the easier it will be to schedule stuff if the earlier date gets chosen. https://discuss.python.org/t/vote-on-possible-steering-council-election-tim…

3 years, 1 month

Licences for PyCharm and other JetBrains products

by Vinay Sajip

Recently I received 20 one-year licenses from JetBrains for the PyCharm IDE (Professional) and other JetBrains products (the licenses cover their "All Products Pack") for use in Python development. There are 11 licenses available - of the licenses I asked for last year, nine people took them up, so those are in use and come out of the allocation of 20. Those of you who took up the licences last time should find that the tools continue to work normally. The licences expire on 27 November 2018. If any others of you are interested in using these licenses, let me know off-list and I will forward the license access details to you. To access the licenses, you will need to have (or create) a JetBrains account. Regards, Vinay Sajip

3 years, 1 month

Python governance vote (December 2018): Results

by ernest＠python.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 # Python governance vote (December 2018) As described in [PEP 8001](https://www.python.org/dev/peps/pep-8001/), the governance election has been completed. The result is that **[PEP 8016: The Steering Council Model (Smith, Stufft)](https://www.python.org/dev/peps/pep-8016/) has been selected as the winner**. - - Supervisor: Ernest W. Durbin III <ernest(a)python.org> - - Announced end of poll: 2018-12-17T12:00:00Z - - Actual time poll closed: 2018-12-17T12:00:02Z - - Authorized voters: 94 ([CPython core developers with a known email-address](https://github.com/python/voters/blob/bb4bceda896c38177e6d9c…) - - Actual votes cast: 62 - - Number of winning choices: 1 - - [Condorcet completion rule](https://civs.cs.cornell.edu/rp.html): Minimax ## Result 1. **[PEP 8016: The Steering Council Model (Smith, Stufft)](https://www.python.org/dev/peps/pep-8016/)** - (Condorcet winner: wins contests with all other choices) 2. [PEP 8012: The Community Governance Model (Langa)](https://www.python.org/dev/peps/pep-8012/) - loses to PEP 8016: The Steering Council Model (Smith, Stufft) by 40–22 3. [PEP 8011: Python Governance Model Lead by Trio of Pythonistas (Wijaya, Warsaw)](https://www.python.org/dev/peps/pep-8011/) - loses to PEP 8016: The Steering Council Model (Smith, Stufft) by 37–20 - loses to PEP 8012: The Community Governance Model (Langa) by 34–28 4. [PEP 8015: Organization of the Python community (Stinner)](https://www.python.org/dev/peps/pep-8015/) - loses to PEP 8016: The Steering Council Model (Smith, Stufft)by 41–18 - loses to PEP 8011: Python Governance Model Lead by Trio of Pythonistas (Wijaya, Warsaw) by 33–24 5. [PEP 8014: The Commons Governance Model (Jansen)](https://www.python.org/dev/peps/pep-8014/) - loses to PEP 8016: The Steering Council Model (Smith, Stufft) by 50–9 - loses to PEP 8015: Organization of the Python community (Stinner) by 38–18 6. [PEP 8010: The Technical Leader Governance Model (Warsaw)](https://www.python.org/dev/peps/pep-8010/) - loses to PEP 8016: The Steering Council Model (Smith, Stufft) by 44–15 - loses to PEP 8014: The Commons Governance Model (Jansen) by 30–28 7. [PEP 8013: The External Council Governance Model (Dower)](https://www.python.org/dev/peps/pep-8013/) - loses to PEP 8016: The Steering Council Model (Smith, Stufft) by 55–6 - loses to PEP 8010: The Technical Leader Governance Model (Warsaw) by 38–17 8. Further discussion - loses to PEP 8016: The Steering Council Model (Smith, Stufft) by 57–4 - loses to PEP 8013: The External Council Governance Model (Dower) by 32–29 ### Result details | | PEP 8016 | PEP 8012 | PEP 8011 | PEP 8015 | PEP 8014 | PEP 8010 | PEP 8013 |Discussion| |----------|----------|----------|----------|----------|----------|----------|----------|----------| | PEP 8016 | - |40 |37 |41 |50 |44 |55 |57 | | PEP 8012 |22 | - |34 |33 |40 |40 |48 |48 | | PEP 8011 |20 |28 | - |33 |42 |42 |52 |51 | | PEP 8015 |18 |22 |24 | - |38 |36 |47 |48 | | PEP 8014 | 9 |18 |16 |18 | - |30 |40 |38 | | PEP 8010 |15 |20 |14 |22 |28 | - |38 |43 | | PEP 8013 | 6 | 9 | 9 |12 |14 |17 | - |32 | |Discussion| 4 |14 |10 |13 |23 |18 |29 | - | ### Ballot report #### Choices - - 0. PEP 8010: The Technical Leader Governance Model (Warsaw) (changelog) - - 1. PEP 8011: Python Governance Model Lead by Trio of Pythonistas (Wijaya, Warsaw) (changelog - - 2. PEP 8012: The Community Governance Model (Langa) (changelog) - - 3. PEP 8013: The External Council Governance Model (Dower) (changelog) - - 4. PEP 8014: The Commons Governance Model (Jansen) (changelog) - - 5. PEP 8015: Organization of the Python community (Stinner) (changelog) - - 6. PEP 8016: The Steering Council Model (Smith, Stufft) (changelog) - - 7. Further discussion #### Ballots in randomized order |0.|1.|2.|3.|4.|5.|6.|7.| |---|---|---|---|---|---|---|---| |8|5|1|7|4|3|2|6| |8|3|2|4|6|5|1|7| |6|1|4|7|5|3|3|8| |3|2|7|5|4|6|1|8| |2|1|4|6|8|5|3|7| |7|2|3|6|4|7|1|5| |8|8|1|3|2|8|3|4| |6|1|2|8|4|3|5|7| |6|1|8|8|8|3|6|7| |6|1|2|7|4|3|5|8| |1|2|6|5|7|4|3|8| |1|5|7|6|3|8|2|4| |2|1|5|8|8|8|6|7| |4|4|3|2|4|4|4|1| |2|1|6|8|5|7|4|3| |4|3|8|7|6|1|2|5| |8|3|4|8|8|4|1|7| |2|1|8|6|4|7|3|5| |3|7|1|8|5|4|2|6| |6|4|3|7|2|5|1|8| |8|4|3|6|7|1|2|5| |8|4|1|8|8|3|2|5| |2|5|1|6|7|4|3|8| |6|5|1|8|4|3|2|7| |8|3|2|7|4|5|1|6| |1|4|2|7|8|3|5|6| |7|1|6|7|1|6|1|8| |4|5|3|6|6|2|1|8| |1|2|7|8|6|4|3|5| |7|6|3|5|4|2|1|8| |7|2|4|6|3|5|1|8| |8|1|4|6|5|3|2|7| |4|2|4|4|3|2|1|8| |5|4|3|7|6|1|2|8| |5|2|1|7|3|4|2|8| |6|1|4|7|5|2|3|8| |1|5|3|2|4|8|6|7| |5|2|4|8|7|6|1|3| |7|3|2|4|1|6|5|8| |5|5|4|7|4|4|3|8| |1|2|7|8|5|3|6|4| |8|4|2|8|1|2|3|8| |5|4|3|7|6|1|2|8| |3|2|8|8|8|4|1|7| |8|4|1|7|6|2|3|5| |7|1|5|8|3|6|2|4| |5|4|3|6|7|2|1|8| |3|2|4|7|6|5|1|8| |3|6|5|8|7|2|1|4| |1|5|4|8|7|2|3|6| |6|5|1|7|4|2|3|8| |8|6|1|4|7|2|3|5| |1|2|8|4|7|6|5|3| |6|6|5|3|4|1|2|8| |1|1|6|7|6|6|1|8| |8|8|1|8|8|8|2|3| |8|5|2|6|6|2|1|4| |8|7|2|4|6|3|1|5| |3|4|2|5|1|6|7|8| |1|8|1|1|8|8|8|8| |3|1|8|8|5|8|2|4| |8|7|1|5|2|3|4|6| #### Rank 1: PEP 8016: The Steering Council Model (Smith, Stufft) (6) - - vs. 1 : (20 - 37) - - vs. 2 : (22 - 40) - - vs. 5 : (18 - 41) - - vs. 0 : (15 - 44) - - vs. 4 : (9 - 50) - - vs. 3 : (6 - 55) - - vs. 7 : (4 - 57) #### Rank 2: PEP 8012: The Community Governance Model (Langa) (2): - - vs. 1 : (28 - 34) - - vs. 5 : (22 - 33) - - vs. 0 : (20 - 40) - - vs. 4 : (18 - 40) - - vs. 7 : (14 - 48) - - vs. 3 : (9 - 48) #### Rank 3: PEP 8011: Python Governance Model Lead by Trio of Pythonistas (Wijaya, Warsaw) (1): - - vs. 5 : (24 - 33) - - vs. 4 : (16 - 42) - - vs. 0 : (14 - 42) - - vs. 7 : (10 - 51) - - vs. 3 : (9 - 52) #### Rank 4: PEP 8015: Organization of the Python community (Stinner) (5): - - vs. 0 : (22 - 36) - - vs. 4 : (18 - 38) - - vs. 3 : (12 - 47) - - vs. 7 : (13 - 48) #### Rank 5: PEP 8014: The Commons Governance Model (Jansen) (4): - - vs. 0 : (28 - 30) - - vs. 7 : (23 - 38) - - vs. 3 : (14 - 40) #### Rank 6: PEP 8010: The Technical Leader Governance Model (Warsaw) (0): - - vs. 3 : (17 - 38) - - vs. 7 : (18 - 43) #### Rank 7: PEP 8013: The External Council Governance Model (Dower) (3): - - vs. 7 : (29 - 32) #### Rank 8: Further discussion (7): - - vs. 3 : (32 - 29) -----BEGIN PGP SIGNATURE----- Comment: what up, i'm ernest. iQIzBAEBCgAdFiEEuSkpynpDar/Z/lqqTxkyLfP/otUFAlwXqjEACgkQTxkyLfP/ otXFhg//dfWINk0dficEu7iL7p/B0YwXD4JQs+uNCag/zmko5tCd4gg/wjLxe6q4 QaB7aSA84Yfrmhe4PIrm4O7doJIyqiObMxFw3N7ZbkAndOPOb2Pkk1ekAaacTTxw lDRPR9CEPDSCtM7ahZsxu1aYHt1BWc7x8NnSyLi7IyN+bcV4viCNky9HYuTnV8i8 ed19ELFDWWlPikFjxXXr/BZA1WL/0rVgC12YtQEy9TvVhZT+kC268sYfuzOLbL6P N2z1sbDYcilXWgH8ahCkyCrcjdySVCjd98TaTCCqCjsj4EO5gy7xf2wWujK0pDBG rct3OESaYtIqTmsItI6P0VIHHJMeZPQ8tnQuqGIgnMMNzjXAMKEmAEvKrzu3sWIN Vtwj3BZMGVw7ZJsuWVvSkesILPtD844R3MvLduWQ4DUuwfu4XyJV04Ws+R2TjsWE gKoL0qk8LAgHVA3D2256wApZltPFLwksf/GaQuYSIJB8+elPOuHbCnqDSsBbEbna LCm6RiEj0ZE6Z3rRxUFxQAwzv0Vpzj+YQFuCGtm3EGZoixJXtai7Aj1lYLI/5NOI /Evhz9LrGN/FNQBY1tOgSIBDstkTMpUWKuIc6t1/T1WOs9iQdJmb4VQO8z0sPtwz KeOeGBFubeb0QZg5CMV2NfhnDDCUW6ROUNzx/fTJt6ea5Ebqd8g= =OTNq -----END PGP SIGNATURE-----

3 years, 1 month

Voting thank you

by Terry Reedy

I just read the PEPs and voted (with a few hours to spare). I want to thank the people who organized the voting, wrote the summary of other projects, wrote the PEPs, and who helped the PEP authors improve the proposals. I like the ranking system. Even if my (mild) first choice (tonight) does not 'win', the rest of my ranks still have an effect on the outcome. I expect I can live with whatever choice the rest of you make. Any change is an experiment. If it does not work, I expect we will try something different. -- Terry Jan Reedy

3 years, 1 month

REMINDER: governance vote is closing by end of this week

by Łukasz Langa

You have time until December 16th AoE to rank proposals and cast your ballot. More information in PEP 8001. Note: reading the candidate PEPs will take you a while. Don't wait until Sunday. - Ł

3 years, 1 month

[RELEASE] Python 3.7.2rc1 and 3.6.8rc1 now available for testing

by Ned Deily

https://blog.python.org/2018/12/python-372rc1-and-368rc1-now-available.html Python 3.7.2rc1 and 3.6.8rc1 are now available. 3.7.2rc1 is the release preview of the next maintenance release of Python 3.7, the latest feature release of Python. 3.6.8rc1 is the release preview of the next and last maintenance release of Python 3.6, the previous feature release of Python. Assuming no critical problems are found prior to 2018-12-20, no code changes are planned between these release candidates and the final releases. These release candidates are intended to give you the opportunity to test the new security and bug fixes in 3.7.2 and 3.6.8. We strongly encourage you to test your projects and report issues found to bugs.python.org as soon as possible. Please keep in mind that these are preview releases and, thus, their use is not recommended for production environments. You can find these releases and more information here: https://www.python.org/downloads/release/python-372rc1/ https://www.python.org/downloads/release/python-368rc1/ -- Ned Deily nad(a)python.org -- []

3 years, 1 month

3.7.2rc1 and 3.6.8rc1 cutoffs ahead, last 3.6.x bugfix release!

by Ned Deily

https://discuss.python.org/t/3-7-2rc1-and-3-6-8rc1-cutoffs-ahead-last-3-6-x… We're reaching the end of the year and it's time for another pair of Python 3 maintenance releases, 3.7.2 and 3.6.8, before we ring out 2018. Since there are still some open release blocker issues and I haven't been bugging you about them, I've moved the code cutoff for the release candidates to this coming Friday, 12-07, by the end of the day (AOE). That gives us all another 4 days to review open issues and PRs. Please give highest attention to any release blockers you have been shepherding or reviewing. Thanks! A reminder: as previously announced, 3.6.8 is planned to be the last bugfix release of the 3.6 series. Python 3.6.0 was released on 2016-12-23, so by the time 3.6.8 is released, 3.6.x will have been in bugfix mode almost exactly 2 years. When a new feature release is made and enters "bugfix" mode, our policy has long been to continue to maintain the previous bugfix branch for at least one more release and then move that branch to "security fix only" mode. 3.7.0 (and 3.6.6) was released nearly six months ago and, with the release of 3.6.8, there will have been two additional 3.6.x bugfix releases since then. So, barring any showstopper issues that might arise, the upcoming 3.6.8rc1 is your last chance to make bugfix changes for 3.6.x. Following the successful release of 3.6.8, only security fixes will be accepted for the 3.6 branch and future 3.6.x releases will be source-only and scheduled as needed; no further binary installers will be produced for 3.6. Refer to the Dev Guide sections and release PEPs linked below for more information. https://devguide.python.org/devcycle/ https://devguide.python.org/#branchstatus https://www.python.org/dev/peps/pep-0494/ https://www.python.org/dev/peps/pep-0537/ -- Ned Deily nad(a)python.org -- []

3 years, 1 month

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-committers December 2018