Mailman 3 July 2019 - python-committers

GitHub: remove the "needs backport to 3.5" label?
by Victor Stinner 20 Aug '19

20 Aug '19

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

6 11

[RELEASE] Python 3.8.0b3 is now available for testing
by Łukasz Langa 30 Jul '19

30 Jul '19

This time without delays, I present you Python 3.8.0b3: https://www.python.org/downloads/release/python-380b3/ <https://www.python.org/downloads/release/python-380b3/> This release is the third of four planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. The next pre-release of Python 3.8 will be 3.8.0b4, the last beta release, currently scheduled for 2019-08-26. Call to action We strongly encourage maintainers of third-party Python projects to test with 3.8 during the beta phase and report issues found to the Python bug tracker <https://bugs.python.org/> as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 and no code changes after 3.8.0rc1, the release candidate. To achieve that, it will be extremely important to get as much exposure for 3.8 as possible during the beta phase. Please keep in mind that this is a preview release and its use is not recommended for production environments. Last beta coming Beta 4 can only be released if all “Release blocker” and “Deferred blocker” issues on bugs.python.org <http://bugs.python.org/> for 3.8.0 are resolved. Please prioritize those for the next four weeks. Acknowledgements Thanks to our binary builders, Ned and Steve, who were very quick today to get the macOS and Windows installers ready. The Windows story in particular got pretty magical, it’s now really fully automatic end-to-end. Thanks to Victor for vastly improving the reliability of multiprocessing tests since Beta 2. Thanks to Pablo for keeping the buildbots green. - Ł

2 1

Please fill in your details in the canonical list of Python core team membership
by Brett Cannon 29 Jul '19

29 Jul '19

Since the discussion of how to define the canonical list of Python core team membership finished (https://mail.python.org/archives/list/python-committers@python.org/thread/M…), I have gone ahead and created the official list. EVERYONE, please go to https://github.com/python/voters/blob/master/python-core.toml and fill in your information (remember you can make changes through GitHub's web UI). Please note that the repository is private and so only fellow core developers or people with admin privileges to the Python org on GitHub can see that file (and if you're curious, it should be in reverse chronological order of joining the team). And everyone has information to fill in except Paul G. and myself (since I added Paul's details when I on-boarded him and I obviously knew all of my details :) . It is important you fill in your details. PEP 13 says active core team members get to vote, have commit access, etc. The plan is to automate adding/removing privileges when we calculate who has been active and so this info will be needed to do that, else empty data will lead to you losing access. FYI the latest this updating of privileges will occur is probably the next steering council election which is slated for October when 3.8.0 goes out. Here's a quick primer to what all the fields mean in the TOML file: - name: self-explanatory ;) (luckily this has turned out to be unique for everyone) - other_names: if you happened to have committed under multiple names (I've filled this in for everyone the best I could, so people shouldn't need to change this) - voting_address: the email address you want voting ballots sent to (this repo is private so use whatever email address you want; currently filled in based on your email address in the last steering council election) - joined: when you joined the core team; I did the best I could based on the developer log, and otherwise calculated it based on your first merge/commit - github: your GitHub username - bpo: your bugs.python.org username - discourse: your discuss.python.org username I'll also mention I created https://github.com/python/voters/blob/master/former-committers.md to keep a record of who has had access to the CPython repo but are not in the Python core team roster. Finally, next steps. With this list done my next plan is to write up a script to use git changes to calculate who has been active. After that I'll write code to take the list of active members and generate the voter roll for steering council elections. From there I'll write some code to generate a new developer log for the devguide with all private info stripped out (e.g. voting email address). Finally, code will be written to help automatically add/remove privileges for (in)active team members.

3 5

Promote Abhilash Raj to core developer
by Barry Warsaw 27 Jul '19

27 Jul '19

I have just posted a poll to Discourse proposing to promote Abhilash Raj to core developer status. https://discuss.python.org/t/vote-to-promote-abhilash-raj-as-core-developer… The topic includes his background, my endorsement, and a list of contributions to CPython. I hope that you will vote to confirm him as a core developer. He will be an excellent addition to our team. Cheers, -Barry

2 1

proposed canonical list of Python core team members
by Brett Cannon 23 Jul '19

23 Jul '19

Since the thread on potential criteria to be kept on the canonical list of core developers has seemingly stopped and no one explicitly objected to the proposed criteria, I gathered together the proposed list of Python core team members (as well as the people who would be left off an why). Please note that since I am working from the git log on the cpython repository and the developer log the data is best-effort, thus if you have information to add, please let all of us know! Also remember this is for the _canonical_ list, not the _active_ list (I plan to start working on that list after all of this is settled). In the text below, "change" means "committed or authored" in git parlance. Details in the form of e.g. "1990-08-09 to 2019-06-11 (11,210)" represent the date of the person's first change, the date of their last change, and the total number of changes made by that person. I have written this to format appropriate in Markdown, so if you view it on Hyperkitty/Mailman3 then it will render appropriately (the link should be in the email footer Mailman adds). # Proposed people to drop from the historical list of Python core team members Be aware that some people show up on multiple lists justifying removal. I thought it was more informative to keep the people in all lists they are in for a more informed decision. The lists are also not in any particular order. The enumeration is there just to point out the total count. Also note that I preemptively pulled people out of lists where I made a judgmental call that their participation was high enough to not warrant potentially be left out of the core team. Obviously if people disagree then please speak up. And as a reminder, the developer log as to why someone was given privileges (if it was written down) is at https://devguide.python.org/developers/. ## People who are in the developer log but have never made a change 1. Santoso Wijaya: 2014-10-29 for Jython 2. Stefan Richthofer: 2014-10-27 for Jython 3. Darjus Loktevic: 2014-07-26 for Jython 4. Chris Angelico: 2014-12-01 for PEP editing 5. Maciej Szulik: 2016-12-23 for bugs.python.org 6. Jeff Allen: 2012-06-13 for Jython 7. Carl Friedrich Bolz: 2011-03-21 for PyPy compatibility 8. Elson Rodriguez: 2011-03-16 for packaging module 9. Kelsey Hightower: 2011-03-16 for packaging module 10. Michael Mulich: 2011-03-16 for packaging module 11. Walker Hale: 2011-03-16 for packaging module 12. Jeff Hardy: 2011-03-14 for IronPython compatibility 13. Maciej Fijalkowski: 2011-03-13 for PyPy compatibility 14. George Boutsioukis: 2010-08-10 for 2to3 15. Paul Kippes: PyCon 2009 for 3to2 16. Ron Duplain: PyCon 2009 for 3to2 17. Allison Randal: 2009 for Parrot compatibility 18. Jim Baker: 2009 for Jython compatibility 19. Gregor Lingl: 2008-06-10 for turtle module 20. Rodrigo Bernardo Pimentel: 2008-04-29 for GSoC 21. Heiko Weinen: 2008-04-29 for GSoC 22. Thomas Lee: 2008-04-21 for AST/optimizer-related branches 23. Jeff Rush: 2008-03-18 for distutils module 24. Chris Monson: 2007-10-20 for editing PEPs 25. Pete Shinners: 2007-03-04 for PEP 3101 in a sandbox 26. Pat Maupin: 2007-02-28 for PEP 3101 work in a sandbox 27. Jackilyn Hoxworth: 2006-05-25 for GSoC 28. Mateusz Rukowicz: 2006-05-30 for GSoC 29. John Benediktsson: 2006-05-17 for Need for Speed sprint 30. Richard Emslie: 2006-05-17 for Need for Speed sprint, relinquished 2008-08-04 31. Runar Petursson: 2006-05-17 for Need for Speed sprint 32. Richard M. Tew: 2006-05-17 for Need for Speed sprint 33. Talin: 2006-04-27 for PEP updates 34. Gregory K. Johnson: 2005-07-08 for GSoC, relinquished 2005-10-16 35. Floris Bruynooghe: 2005-07-08 for GSoC, relinqguished 2005-07-14 36. Eric Price: 2003-05-02 for decimal module, relinquished 2005-04-10 37. Roy Smith: Relinquished 2008-08-04 38. Irmen de Jong: Relinquished 2005-04-10 ## GSoC students If you are aware of someone who should be on this list, please speak up. This was pulled from the developer log and my own knowledge. 1. Robert Schuppenies: 2008-06-01 to 2009-05-17 (22) 2. Rodrigo Bernardo Pimentel: no commits 3. Heiko Weinen: no commits 4. Matt Fleming: 2006-07-28 to 2006-07-29 (2) 5. Jackilyn Hoxworth: no commits 6. Mateusz Rukowicz: no commits 7. Gregory K Johnson: no commits 8. Floris Bruynooghe: no commits 9. Anish Shah: 2016-02-06 to 2017-03-03 (2) ### Leaving off The following people were GSoC students but seemingly continued to contribute, and so are being left off the list of people to drop due to GSoC participation. 1. Guilherme Polo: 2008-05-24 to 2009-08-18 (92) 2. Senthil Kumaran: 2008-06-22 to 2019-04-09 (1,252) 3. Alexandre Vassalotti: 2007-06-07 to 2013-12-07 (335) ## Sprinters If you are aware of someone who should be on this list, please speak up. This was pulled from the developer log and my own knowledge. 1. Jerry Seutter: 2008-03-25 to 2008-04-08 (4) 2. Andrew Dalke: 2006-05-24 to 2006-05-27 (18) 3. John Benediktsson: no commits 4. Martin Blais: 2006-05-26 to 2006-06-06 (4) 5. Richard Emslie: no commits 6. Runar Petursson: no commits 7. Richard M. Tew: no commits 8. Nicholas Bastin: 2004-03-21 to 2004-09-29 (27) ### Leaving off The following people were granted commit privileges at a sprint but continued to actively participate. 1. Andrew Svetlov: 2012-03-13 to 2019-07-05 (580) 2. Jason R. Coombs: 2011-07-26 to 2019-07-07 (155) 3. Jack Diederich: 2006-05-25 to 2010-02-23 (33) 4. Kristján Valur Jónsson: 2006-05-25 to 2015-09-12 (227) 5. Steve Holden: 2002-06-14 to 2007-04-26 (15) 6. Richard Jones: 2006-05-23 to 2010-08-15 (14) 7. Christian Tismer: 2002-05-28 to 2018-06-10 (9) ## People who committed for less than 3 months 1. Tommy Beadle: 2016-06-02 to 2016-06-02 (2) 2. Alessandro Cucci: 2015-07-28 to 2015-07-28 (1) 3. Dingyuan Wang: 2015-06-21 to 2015-06-21 (1) 4. Daniel Holth: 2014-01-02 to 2014-01-02 (1) 5. Felix Crux: 2013-08-12 to 2013-08-12 (4) 6. Zbigniew Jędrzejewski-Szmek: 2012-09-02 to 2012-09-02 (1) 7. Atsuo Ishimoto: 2012-07-15 to 2012-07-15 (1) 8. Ralf Schmitt: 2011-05-31 to 2011-05-31 (2) 9. Ask Solem: 2010-11-09 to 2010-11-09 (6) 10. Charles G. Waldman: 2001-01-10 to 2001-01-10 (1) 11. Nicholas Riley: 2000-09-23 to 2000-09-23 (2) 12. David Scherer: 2000-08-14 to 2000-08-14 (1) 13. Andrew Dalke: 2006-05-24 to 2006-05-27 (18) 14. Dirkjan Ochtman: 2010-02-23 to 2010-03-04 (6) 15. Martin Blais: 2006-05-26 to 2006-06-06 (4) 16. Dave Cole: 2004-08-08 to 2004-08-25 (6) 17. Alexis Métaireau: 2011-05-04 to 2011-05-30 (2) 18. Reid Kleckner: 2011-03-14 to 2011-04-10 (14) 19. Žiga Seilnacht: 2007-03-11 to 2007-04-12 (15) 20. David Ascher: 2004-02-17 to 2004-03-26 (2) 21. Edward Loper: 2004-08-08 to 2004-09-30 (42) 22. Vladimir Marangozov: 2000-07-09 to 2000-09-08 (22) 23. Roger Serwy: 2013-03-30 to 2013-06-11 (39) # Proposed list of core developers This list is sorted by timespan of contribution, i.e. date of last change - date of first change. If you find any duplicate names, please let me know as I have a file going where I tried to amalgamate peoples' names to connect changes made under some variation of their name. And obviously if you are missing from the list and should be there then please speak up so I can figure out what went wrong. 1. Peter Moody: 2013-10-21 to 2014-03-11 (5) 2. Stefan Behnel: 2019-01-02 to 2019-06-01 (21) 3. Chris Jerdonek: 2012-09-24 to 2013-02-27 (153) 4. Roger E. Masse: 1996-12-09 to 1997-06-05 (79) 5. Johannes Gijsbers: 2004-08-14 to 2005-03-12 (74) 6. Tony Lownds: 2002-09-22 to 2003-05-17 (18) 7. Daniel Stutzbach: 2010-08-22 to 2011-05-04 (38) 8. Hynek Schlawack: 2012-05-15 to 2013-02-04 (96) 9. Samuele Pedroni: 2003-05-16 to 2004-02-21 (3) 10. Travis E. Oliphant: 2007-08-18 to 2008-06-06 (14) 11. Doug Hellmann: 2009-09-20 to 2010-07-21 (7) 12. Steven M. Gava: 2001-06-25 to 2002-06-10 (97) 13. Josiah Carlson: 2008-06-09 to 2009-06-03 (23) 14. Moshe Zadka: 2000-07-28 to 2001-07-23 (40) 15. Carol Willing: 2018-06-05 to 2019-06-20 (13) 16. Mark Summerfield: 2007-08-16 to 2008-09-08 (31) 17. Bill Janssen: 2007-08-29 to 2008-09-29 (36) 18. Chui Tey: 2001-10-31 to 2002-12-12 (10) 19. Finn Bock: 2001-08-23 to 2002-11-06 (14) 20. Guilherme Polo: 2008-05-24 to 2009-08-18 (92) 21. George Yoshida: 2006-04-17 to 2007-08-15 (50) 22. Martin Panter: 2015-08-24 to 2017-01-29 (761) 23. Sandro Tosi: 2011-08-02 to 2013-01-26 (285) 24. Mark Shannon: 2017-10-22 to 2019-05-07 (3) 25. Paul Ganssle: 2017-11-09 to 2019-06-18 (20) 26. Nathaniel J. Smith: 2017-02-12 to 2018-09-21 (18) 27. Emily Morehouse: 2017-06-13 to 2019-02-01 (6) 28. Petr Viktorin: 2017-11-08 to 2019-07-05 (40) 29. Paul Prescod: 2000-06-30 to 2002-03-17 (20) 30. Ross Lagerwall: 2011-03-14 to 2012-12-13 (77) 31. Pablo Galindo: 2017-09-07 to 2019-07-01 (152) 32. Cheryl Sabella: 2017-08-14 to 2019-06-17 (120) 33. Julien Palard: 2017-08-08 to 2019-07-08 (65) 34. Dino Viehland: 2017-06-21 to 2019-05-28 (6) 35. Jean-Paul Calderone: 2010-04-10 to 2012-03-16 (16) 36. Stéphane Wirtel: 2017-05-22 to 2019-06-01 (60) 37. Jesse Noller: 2008-06-18 to 2010-07-03 (99) 38. Lisa Roach: 2017-04-04 to 2019-05-20 (16) 39. Peter Schneider-Kamp: 2000-07-10 to 2002-08-27 (45) 40. Jeroen Ruigrok van der Werven: 2008-04-16 to 2010-07-13 (55) 41. Richard Oudkerk: 2012-04-30 to 2014-07-28 (220) 42. Hirokazu Yamamoto: 2008-08-13 to 2010-12-09 (344) 43. Ivan Levkivskyi: 2017-02-13 to 2019-07-09 (66) 44. Mariatta: 2017-02-01 to 2019-07-11 (203) 45. Tarek Ziadé: 2008-12-24 to 2011-06-02 (832) 46. Davin Potts: 2016-09-07 to 2019-02-25 (8) 47. Steven D'Aprano: 2015-11-30 to 2018-05-19 (43) 48. Eric S. Raymond: 2000-07-10 to 2002-12-31 (93) 49. David Malcolm: 2010-11-05 to 2013-05-06 (15) 50. Peter Astrand: 2004-10-21 to 2007-05-26 (33) 51. Xiang Zhang: 2016-11-23 to 2019-07-07 (126) 52. Nadeem Vawda: 2011-04-12 to 2013-12-08 (229) 53. Steve Purcell: 2001-03-22 to 2003-12-06 (18) 54. Inada Naoki: 2016-10-05 to 2019-07-11 (327) 55. Jeffrey Yasskin: 2007-08-22 to 2010-07-09 (85) 56. Xavier de Gaye: 2016-06-15 to 2019-05-30 (136) 57. Petri Lehtinen: 2011-10-23 to 2014-10-10 (188) 58. Jason Tishler: 2002-05-15 to 2005-05-19 (34) 59. Steven Bethard: 2008-03-17 to 2011-04-03 (58) 60. Collin Winter: 2007-03-08 to 2010-04-16 (174) 61. Andrew McNamara: 2003-06-08 to 2006-07-30 (27) 62. Frank Wierzbicki: 2009-08-02 to 2013-01-16 (12) 63. Greg Stein: 1999-11-07 to 2003-06-23 (29) 64. Jack Diederich: 2006-05-25 to 2010-02-23 (33) 65. Florent Xicluna: 2010-02-26 to 2014-01-21 (398) 66. Bob Ippolito: 2005-03-28 to 2009-03-29 (44) 67. Jim Fulton: 2000-10-06 to 2004-10-13 (30) 68. Paul Moore: 2015-03-22 to 2019-03-30 (12) 69. Piers Lauder: 2001-07-20 to 2005-08-31 (34) 70. Eli Bendersky: 2011-01-13 to 2015-03-14 (379) 71. Gustavo Niemeyer: 2002-11-05 to 2007-01-10 (60) 72. Richard Jones: 2006-05-23 to 2010-08-15 (14) 73. Armin Ronacher: 2008-06-10 to 2012-10-07 (15) 74. Alex Martelli: 2003-04-22 to 2007-08-22 (25) 75. Robert Collins: 2014-10-17 to 2019-05-22 (109) 76. Meador Inge: 2011-09-20 to 2016-04-30 (105) 77. Amaury Forgeot d'Arc: 2007-11-10 to 2012-07-08 (499) 78. Steve Dower: 2014-10-08 to 2019-07-01 (811) 79. Charles-François Natali: 2011-05-20 to 2016-02-10 (366) 80. Trent Nelson: 2008-03-17 to 2012-12-12 (97) 81. Steve Holden: 2002-06-14 to 2007-04-26 (15) 82. Berker Peksağ: 2014-06-29 to 2019-05-31 (1,043) 83. Philip Jenvey: 2009-05-07 to 2014-04-18 (63) 84. Tal Einat: 2014-07-16 to 2019-07-11 (67) 85. Michael Foord: 2009-04-01 to 2014-04-15 (333) 86. Gerhard Häring: 2006-04-23 to 2011-05-09 (46) 87. Kushal Das: 2014-04-15 to 2019-05-17 (20) 88. Donald Stufft: 2013-12-20 to 2019-03-06 (108) 89. Michael W. Hudson: 2001-08-27 to 2006-11-23 (272) 90. Ken Manheimer: 1998-03-03 to 2003-06-17 (7) 91. Hye-Shik Chang: 2003-12-09 to 2009-04-02 (145) 92. Anthony Baxter: 2001-12-20 to 2007-04-17 (182) 93. Yury Selivanov: 2014-01-27 to 2019-06-22 (1,045) 94. David Wolever: 2008-03-18 to 2013-08-14 (9) 95. Zachary Ware: 2013-11-03 to 2019-06-04 (666) 96. Just van Rossum: 1999-01-22 to 2004-11-12 (351) 97. Ethan Furman: 2013-06-14 to 2019-07-04 (155) 98. David Goodger: 2003-01-02 to 2009-01-31 (10) 99. Fredrik Lundh: 2000-06-29 to 2006-08-16 (314) 100. Serhiy Storchaka: 2012-12-27 to 2019-06-26 (4,212) 101. Alexandre Vassalotti: 2007-06-07 to 2013-12-07 (335) 102. Andrew MacIntyre: 2002-02-16 to 2008-09-30 (125) 103. Phillip J. Eby: 2004-03-24 to 2010-12-03 (60) 104. Eric Snow: 2012-09-05 to 2019-06-01 (180) 105. Trent Mick: 2000-06-06 to 2007-04-13 (32) 106. Neal Norwitz: 2001-12-19 to 2009-01-04 (1,815) 107. Andrew Svetlov: 2012-03-13 to 2019-07-05 (580) 108. Ka-Ping Yee: 2000-10-03 to 2008-03-20 (101) 109. Jeremy Kloth: 2011-09-12 to 2019-03-06 (6) 110. Sean Reifschneider: 2004-09-17 to 2012-03-12 (42) 111. Ronald Oussoren: 2006-03-30 to 2014-02-06 (553) 112. Alex Gaynor: 2011-07-17 to 2019-06-15 (27) 113. Larry Hastings: 2010-02-24 to 2018-01-28 (434) 114. Jason R. Coombs: 2011-07-26 to 2019-07-07 (155) 115. Tim Golden: 2010-08-06 to 2018-07-28 (90) 116. Jesús Cea: 2008-05-13 to 2016-09-19 (294) 117. Alexander Belopolsky: 2010-05-26 to 2018-10-05 (419) 118. Ned Deily: 2010-11-27 to 2019-07-02 (938) 119. Łukasz Langa: 2010-11-10 to 2019-06-17 (212) 120. Terry Jan Reedy: 2010-11-10 to 2019-07-09 (1,304) 121. Éric Araujo: 2010-08-13 to 2019-05-03 (1,082) 122. Brian Quinlan: 2010-09-18 to 2019-06-28 (26) 123. Brian Curtin: 2010-03-25 to 2019-01-18 (428) 124. Giampaolo Rodolà: 2010-04-18 to 2019-05-29 (250) 125. Stefan Krah: 2010-04-01 to 2019-07-10 (556) 126. Kristján Valur Jónsson: 2006-05-25 to 2015-09-12 (227) 127. Victor Stinner: 2010-01-29 to 2019-07-09 (6,011) 128. Kurt B. Kaiser: 2001-07-03 to 2011-05-25 (502) 129. Thomas Heller: 2000-09-07 to 2010-08-08 (758) 130. Ezio Melotti: 2009-06-25 to 2019-06-02 (2,000) 131. Chris Withers: 2009-04-11 to 2019-05-07 (21) 132. R. David Murray: 2009-03-30 to 2019-05-22 (2,111) 133. Facundo Batista: 2004-10-16 to 2015-04-22 (159) 134. Senthil Kumaran: 2008-06-22 to 2019-04-09 (1,252) 135. Antoine Pitrou: 2008-07-22 to 2019-07-01 (3,824) 136. Georg Brandl: 2005-06-03 to 2016-08-15 (5,677) 137. Benjamin Peterson: 2008-03-25 to 2019-07-11 (5,897) 138. Mark Dickinson: 2008-01-08 to 2019-06-16 (1,926) 139. Jeremy Hylton: 1997-08-13 to 2009-03-31 (1,022) 140. Christian Heimes: 2007-10-31 to 2019-07-02 (1,354) 141. Eric V. Smith: 2007-08-24 to 2019-06-20 (507) 142. Armin Rigo: 2003-10-24 to 2017-04-13 (138) 143. Nick Coghlan: 2005-11-16 to 2019-06-21 (808) 144. Jack Jansen: 1992-08-13 to 2006-04-20 (2,978) 145. Matthias Klose: 2004-08-04 to 2018-04-30 (408) 146. Martin v. Löwis: 2000-09-08 to 2015-02-08 (2,772) 147. Sjoerd Mullender: 1992-08-04 to 2007-01-16 (152) 148. Vinay Sajip: 2004-02-20 to 2019-07-01 (1,157) 149. Lars Gustäbel: 2000-09-21 to 2016-04-19 (173) 150. Mark Hammond: 2000-06-08 to 2016-01-10 (153) 151. Christian Tismer: 2002-05-28 to 2018-06-10 (9) 152. Brett Cannon: 2003-04-18 to 2019-07-05 (2,140) 153. Greg Ward: 1998-12-18 to 2015-04-20 (852) 154. Marc-André Lemburg: 2000-06-07 to 2017-02-24 (345) 155. Thomas Wouters: 2000-07-14 to 2017-05-22 (350) 156. Raymond Hettinger: 2002-05-11 to 2019-06-24 (4,144) 157. Walter Dörwald: 2002-03-21 to 2019-06-06 (528) 158. Skip Montanaro: 2000-06-29 to 2018-05-18 (672) 159. Neil Schemenauer: 2000-09-15 to 2019-07-10 (326) 160. Tim Peters: 2000-06-30 to 2019-07-10 (2,511) 161. Gregory P. Smith: 2000-05-11 to 2019-06-29 (1,271) 162. Andrew Kuchling: 1998-04-09 to 2019-03-03 (2,140) 163. Fred Drake: 1996-07-23 to 2018-06-06 (5,469) 164. Barry Warsaw: 1994-07-25 to 2019-07-03 (2,102) 165. Guido van Rossum: 1990-08-09 to 2019-06-11 (11,210)

4 6

Steering Council Update for July 2019
by Carol Willing 09 Jul '19

09 Jul '19

I've posted an update from the Steering Council to our repo: https://github.com/python/steering-council/blob/master/updates/2019-07-08_s… I will also link to this on python-dev and on Discourse (discuss.python.org ). For completeness, below is the full text. # Steering Council Update ## Date: 2019-07-08 Steering Council updates will be posted irregularly and as needed. We provide these updates to foster open and transparent communication about Steering Council activity. We strive to post at least once every month. # Message from the Steering Council Sorry we've been silent for a while! With PyCon in Cleveland, the Language Summit, Sprints, PEP activity, and a Python 3.8 beta release, it's been a busy and productive May and June. Thank you all for your contributions. Below are some of the outcomes of our weekly Steering Council conversations. --- ## Mandate This section organizes Steering Council (SC) activity and projects using the mandates listed in PEP 13. ### Language > Maintain the quality and stability of the Python language and CPython interpreter - Inspired by Russell Keith-Magee's PyCon keynote about Black Swan events, the Steering Council is looking at what may impact Python for the next decade. We have been discussing this within the Steering Council and writing up some thoughts on major challenges facing Python. We'll continue to edit and polish this vision document and share it when we are ready for wider comment. ### Contributors > Make contributing as accessible, inclusive, and sustainable as possible - **Communications channels:** We are very pleased with the move of python-dev, etc. to Mailman 3. We now have a modern UI and easy search across mailing lists. Just a reminder to recap where announcements and conversations are taking place: - To reach core committers specifically, we will use python-committers(a)python.org. - To reach the entire Python developer community, we will use python-dev(a)python.org. - For specific requests to the SC (e.g., PEP reviews), please use our public GitHub tracker at https://github.com/python/steering-council/issues. - To reach just the SC, you can email us at steering-council(a)python.org. - We will also occasionally use Discourse, at https://discuss.python.org (for example, Discourse is useful for polls and votes). ### PEPs > Establish appropriate decision-making processes for PEPs - To request a PEP review, please file an issue on the [SC issue tracker](https://github.com/python/steering-council/issues). PEP highlights include: - PEP 570, "Python Positional-Only Parameters", by Larry Hastings, Pablo Galindo and others. *Appointed Guido van Rossum as BD.* "Completed." - PEP 574, "Pickle protocol 5 with out-of-band data", Antoine Pitrou. *Appointed Nick Coghlan as BD.* "Marked Final." - PEPs 576, 579, 580, 590 (competing PEPs on C function call optimizations by Mark Shannon and Jeroen Demeyer; note that PEP 576 is withdrawn in favor of PEP 590). *Appointed Petr Viktorin as BD.* "Accepted 590." - PEP 578, "Python Runtime Audit Hooks", Steve Dower. *Appointed Christian Heimes as BD.* "Landed, about to be marked Final." ### Interaction with PSF > Formalize and maintain the relationship between the core team and the PSF - We began discussions about fundraising ideas for CPython projects and administrative support. - A [donation page]([https://www.python.org/psf/donations/python-dev/](https://www.python… was created by the PSF and was linked from the [CPython repo]([https://github.com/python/cpython](https://github.com/python/cpython…. Any funds that are donated will be used for Core Developers to attend the core development sprints (to start; future possibilities are dependent on the amount of funds gathered). - At the Steering Council's recommendation, the PSF also is looking at hiring a Project Manager to manage communication and some logistics for the 2020 Python 2.7 End of Life. - The PSF Code of Conduct Workgroup is working on a revision of the CoC and its approval by the PSF board. Brett and Carol serve on the Workgroup. ### Governance > Seek consensus among contributors and the core team before acting in a formal capacity, > Act as a "court of final appeal" for decisions where all other methods have failed. - The weekly SC meeting cadence (Tuesdays 3-4pm US West Coast time) has been working out well. --- ## Reference This reference section summarizes the Steering Council's mandate and powers. ### Mandate (PEP 13) The steering council shall work to: - Maintain the quality and stability of the Python language and CPython interpreter, - Make contributing as accessible, inclusive, and sustainable as possible, - Formalize and maintain the relationship between the core team and the PSF, - Establish appropriate decision-making processes for PEPs, - Seek consensus among contributors and the core team before acting in a formal capacity, - Act as a "court of final appeal" for decisions where all other methods have failed. ### Powers (PEP 13) The council has broad authority to make decisions about the project. For example, they can: - Accept or reject PEPs - Enforce or update the project's code of conduct - Work with the PSF to manage any project assets - Delegate parts of their authority to other subcommittees or processes

2 2

[RELEASE] Python 3.7.4 is now available
by Ned Deily 09 Jul '19

09 Jul '19

Python 3.7.4 is now available. 3.7.4 is the next maintenance release of Python 3.7, the latest feature release of Python. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-374/ 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.4 can be found in its change log: https://docs.python.org/3.7/whatsnew/changelog.html#python-3-7-4-final https://docs.python.org/3.7/whatsnew/3.7.html 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://www.python.org/psf/ -- Ned Deily nad(a)python.org -- []

1 0

[RELEASE] Python 3.8.0b2 is now available for testing
by Łukasz Langa 09 Jul '19

09 Jul '19

After a few days of delay, but somewhat cutely timed with the US Independence Day, I present you Python 3.8.0b2: https://www.python.org/downloads/release/python-380b2/ <https://www.python.org/downloads/release/python-380b2/> This release is the second of four planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. The next pre-release of Python 3.8 will be 3.8.0b3, currently scheduled for 2019-07-29. Call to action We strongly encourage maintainers of third-party Python projects to test with 3.8 during the beta phase and report issues found to the Python bug tracker <https://bugs.python.org/> as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 and no code changes after 3.8.0rc1, the release candidate. To achieve that, it will be extremely important to get as much exposure for 3.8 as possible during the beta phase. Please keep in mind that this is a preview release and its use is not recommended for production environments. No more non-bugfixes allowed on the “3.8” branch The time has come, team. Please help make Python 3.8 as stable as possible and keep all features not currently landed for Python 3.9. Don’t fret, it’ll come faster than you think. - Ł

2 1

Cleaning up the historical list of core developers
by Brett Cannon 05 Jul '19

05 Jul '19

To simplify the developer log and to have an accurate list of core developers for PEP 13, I have been trying to compile a clean, historical list of core developers. Unfortunately it turns out the developer log is a bit messy and incomplete (hence why I would say that I have *a* list, but not necessary *the* list). :) For instance, I know for a fact people were granted commit rights at sprints but not recorded in the developer log (I found at least one instance where I personally forgot). I suspect the same happened for GSoC. We also have people listed in the developer log who were never meant to be core developers but were given access due to the shared nature of hg.python.org (e.g. the Jython devs getting access due to hg.python.org hosting the Jython source code). All of this is to say that the developer log is incomplete, and that means relying on the git history to help clean this up for figuring out who was purposefully made a core dev is impossible. And honestly this is understandable as it wasn't that important whether you were a core dev or not pre-PEP 13 other than security access (which we somewhat got for free when we changed version control systems and people fell off from commit access). But now with PEP 13 the historical list of core developers is important as that defines whether you are able to qualify to vote. Or put another way, an analogy I have been using is the historical list of core developers defines "citizenship" in the Python core team and active status means you are "registered to vote". So, how do we pull together a clean-enough list of historical core developers? Here is my idea of criteria of people to be on the list (based on the developer log and the git log): - Was not a GSoC student (clarification to follow for those who fall into this category and are actually active) - People who were not granted commit rights at a sprint just for being at a sprint (clarification to follow) - Did not commit/author beyond a 3 month time span from first commit/authorship to last commit/authorship and their last commit was more than two years ago (helps cover people we don't have good records for in terms of sprints or GSoC who never got involved) - Anyone who falls into the above cases and requests to be considered an official core developer (so people who fall into the above buckets can get pulled out based on the fact that they did become active) Once we have reached consensus around the criteria I can generate a list of people who would be on the list and who wouldn't and we can handle requests to be re-classified. Then I will commit the lists to the voters repository and regenerate the developer log. BTW I'm expecting this entire exercise to be a one-time thing and that all future core developers will be immediately added to the canonical list of core devs so it doesn't become inaccurate again.

5 9

[RELEASE] Python 3.7.4rc2 is now available for testing
by Ned Deily 03 Jul '19

03 Jul '19

Python 3.7.4rc2 is now available. 3.7.4rc2 is the second release preview of the next maintenance release of Python 3.7, the latest feature release of Python. Assuming no further critical problems are found prior to 2019-07-08, no code changes are planned between this release candidate and the final release. The release candidate is intended to give you the opportunity to test the new security and bug fixes in 3.7.4. Because of the small number of changes between rc1, the original release preview, and rc2, we are planning on an abbreviated exposure cycle so we can get the final release to you as soon as possible. We strongly encourage you to test your projects and report issues found to https://bugs.python.org/ as soon as possible. Please keep in mind that this is a preview release and, thus, is not recommended for production environments. You can find the release files, a link to the changelog, and more information here: https://www.python.org/downloads/release/python-374rc2/ -- Ned Deily nad(a)python.org -- []

1 1