Thread by @mariatta

#PyConUS2022 Python SC (Steering Council) panel.
We have @pyblogsal and @Yhg1s from the SC joining us today.
Agenda:
- What is the SC?
- Highlights of the year?
- What's new in Python 3.11
- pre-recorded Q&A

#PyConUS2022 Python SC Agenda:
SC is defined in PEP 13: in charge of the python programming language, and CPython implementation
Govern by consensus. Fosters the community and the core devs.
Final decision on PEPs (Python Enhancement Proposals), except those delegated.

#PyConUS2022 Python SC
The SC meets weekly. SC is separate from PSF but have very good working relationship.
Monthly updates published in
github.com/python/steerin…
Write to them at steering-council at python dot org

#PyConUS2022 Python SC
SC has conflict of interest policy. We can't have more than two SC members from the same company. (2 SC members are Googlers!: @gpshead and @Yhg1s

Thomas acknowledges that the current SC are currently five men in tech. Not diverse.

#PyConUS2022 Python SC
The diversity is a reflection of the core devs.
You don't have to be a core dev to be the SC, but core devs are the only ones who can vote.
There is a trust issue.
Thomas would love to see non core-dev as SC.
We want to improve.

#PyConUS2022 Python SC
Highlights of the year:
bugs.python.org has been migrated to GitHub issues!! YAY!!! It was years of planning, see PEP 581, 588 (from 2018)
Thanks to the support from GitHub and PSF, as well as work of Ezio and @llanga

#PyConUS2022 Python SC
@ThePSF hired @llanga as the Developer in Residence.
@google funded this year, and @Meta is funding the next year.
The role is to work through issues and pull requests, mentoring.

#PyConUS2022 Python SC
There's been multiple efforts to speed up CPython:
@microsoft's Faster CPython team, @instagram's Cinder, and Sam Gross's "nogil" branch.

#PyConUS2022 Python SC
3.11 has lots of new things!
Faster CPython, self type, exception groups and except*, more error message improvements!

#PyConUS2022 Python SC
New in Python 3.11: PEP 657: peps.python.org/pep-0657/
the error 'NoneType' object is not subscriptable, now it tells you which one!

#PyConUS2022 Python SC
Exception groups and except* is in PEP 654:
peps.python.org/pep-0654
Lots people have been waiting for this, we're bringing this in from Trio.
The exception group will help with handling taskgroup cancellations.

#PyConUS2022 Python SC
Lots of Typing improvements.
from typing import Self
to annotate functions that returns the type of its own class.

#PyConUS2022 Python SC
We now have LiteralString type
from typing import LiteralString

#PyConUS2022 Python SC
import tomllib

Support for parsing TOML in the standard lib so you don't have to import third party library

#PyConUS2022 Python SC
Q: What are Sc plans to put Python in the browser (WASM)?
A: We don't need to plan anymore. Go watch @pwang's keynote and checkout @pyscript_dev

#PyConUS2022 Python SC
Q: CPython 3.11 shows a noticeable performance over 3.10. How much faster 3.12 going to be?
A: "It depends". But will be even faster for sure.
As Release manager, Pablo usually tries to

#PyConUS2022 Python SC
Q: How beneficial has it been to have a Dev-in-residence? Any plan for expanding?
A: It has been great success! We would like to have 3 or more. We're looking for funding.
There is a question we're open to hire non core dev.

#PyConUS2022 Python SC
Q: Will Sam Gross's nogil branch be viable for CPython? Is there a roadmap?
A: We don't have roadmap, but we're excited about it. We still have lots of questions. It definitely not easily integrate to the core. We will need a roadmap. We'd like to see PEP.

#PyConUS2022 Python SC
Q: What happened with HPy? Any other initiatives to address this problem?
A: HPy is effort to define C-API for CPython and other Python implementations. It is still being developed, it takes a lot of time.

#PyConUS2022 Python SC
Q: What does the SC think of the progress of attracting new contributors and from minority groups?
A: SC and core devs are aware of this, some of them actively mentoring minority groups. We know we have a lot to do, but it is important today

#PyConUS2022 Python SC
Q: Any uptick of new contributors post GiHub migration?
A: We just migrated to GH issue in two weeks. A bit difficult to say. We're still figuring out new policy and workflows.

#PyConUS2022 Python SC
Q: In 3.10 we got better error messages. Are there further improvements? Any idea to steal from other languages?
A: Yes expect more for sure! This is important for especially new learners... but no, we're not stealing (from rust) 😉 Rust still has it.

#PyConUS2022 Python SC
Q: Are the core devs generally happy with the SC election system? Would any of you like something to change on it?
A: SC election happens after the next major release.
@Yhg1s personally would like to see 2-3 year term, or overlapping term.

#PyConUS2022 Python SC
SC Cannot change how the SC works. Core devs need to decide.

#PyConUS2022 Python SC
Q: Typing and packaging PEPs have been delegated. Is this working out?
A: It has been working well so far. We delegate to people we trust. We can't always review all the PEPs.