- The SC and the Developer-in-Residence discussed ongoing PR reviews, release blockers for 3.11, documenting the whole Python release process, and the mandate to require 2FA.
- The SC discussed ongoing issues with the Python 3.11 betas, release blockers, unexpected slowdowns in tracing mode and with enums.
- The SC discussed moving some parts of python-dev to discourse and what challenges this entails.
- 4 SC members present
- The SC discussed who should have admin access to the python GitHub org
and the various
python/
repos. - The SC acknowledged the release blockers such as the tracing performance.
- The SC discussed the composition of the Python Security Response Team (PSRT).
- The SC discussed that organizations want to give the PSF money for Security work.
- The SC discussed Python Core Dev Sprint hosting, October timeframe.
- The SC discussed using Github Projects for steering council work visibility.
- The SC scheduled a talk with the new manager of Microsoft's Faster CPython team.
- The SC discussed more on what GitHub
python/
org should contain. PSF license CLA requirement is per org and projects that aren't strictly CPython don't feel right in there. - The SC discussed Discourse long term needs for sustainability.
- The SC discussed the status of typing annotation PEPs (649 (Deferred Evaluation Of Annotations Using Descriptors) and 563 (Postponed Evaluation of Annotations)) and who to get input from.
- The SC and the Developer-in-Residence again discussed ongoing PR reviews, release blockers for 3.11, documenting the whole Python release process, as well as the new CLA process on GitHub.
- The SC and the DiR had a long discussion about PEP 563 (Postponed Evaluation of Annotations) and PEP 649 (Deferred Evaluation Of Annotations Using Descriptors), and possible long-term solutions.
- The SC again discussed ongoing issues with the Python 3.11 betas, release blockers, unexpected slowdowns in tracing mode and with enums.
- The SC met with Michael Droetboom, manager of Microsoft’s Faster CPython team, and talked about the challenges of having a team of full-timers working together with volunteers, large features that need long-term planning, and handling a large amount of changes with unforeseen consequences.
- The SC discussed moving from python-dev to discuss.python.org.
- The SC discussed a request for extra privileges for the
python
GitHub organization, and decided that since the organization is currently not limited to CPython-related repos, it’s best to keep the list of owners minimal. - The SC discussed guidelines for repositories in the python GitHub organization.