You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In alphabetical order by title, schedule coming soon!
19
+
20
+
### **A Roadmap for Rust for CPython** — David Hewitt
21
+
22
+
The Rust for CPython project would like to present the current state of the project and the plans as we head towards a PEP. We will cover the roadmap we are working towards as well as the design choices for the "internal Rust API". We'd like to invite discussion to shape the project. Do attendees agree with the proposed scope for the initial implementation? What success criteria would attendees like to see if Rust were to become permanent? Should more exotic designs be explored for the Rust API?
23
+
24
+
### **Developer in Residence update & future** — Petr Viktorin
25
+
26
+
A big part of the Developer in Residence role should be helping other core devs, so they can focus volunteer time on enjoyable tasks. What are the best ways to do that?
27
+
28
+
### **GC: Generational? Incremental? Both.** — Mark Shannon
29
+
30
+
The incremental GC was reverted for 3.14, due to negative performance impact on some applications. But that reversion had a [negative performance impact on other code](https://discuss.python.org/t/reverting-the-incremental-gc-in-python-3-14-and-3-15/107014/59).
31
+
32
+
I want to show a bit of theory to show that a GC that is both generational and incremental is both possible and provably as good or better at collecting young cycles as the current generational-only GC.
33
+
34
+
### **Improving the Python buffer protocol** — Nathan Goldbaum
35
+
36
+
I will propose an effort for Python 3.16 to improve the buffer protocol. I'm interested in adding a protocol for projects to export and consume buffers with types that aren't known to CPython, removing Python from its position as arbiter of what data types are supported by the buffer protocol and what aren't. I'd also like to add Rust-like mutability semantics with 1 writer XOR 1 or more readers allowed per buffer.
37
+
38
+
Additionally, I'd like to generally improve the documentation for the buffer protocol in CPython. I think there should be reference docs that replace PEP 3118 as the authoritative source of truth for the semantics of the buffer protocol.
39
+
40
+
### **Memory snapshots and the CPython runtime** — Hood Chatham
41
+
42
+
Various WebAssembly Python distributions (both Cloudflare and Fastly) are using memory snapshots to improve Python startup time. This leads to complications around entropy use at startup. For example, the dictionary hash seed is chosen at startup and cannot be changed later so we give up hash randomization. Should Python expose an API to reseed dictionaries after startup?
43
+
44
+
Taking a memory snapshot introduces two separate stages of execution: initialization time vs execution time. In order to work, client code may need to know The Python language model has no concept of initialization time, there is only runtime. Faster alternative implementations like PyPy and GraalPython introduce this distinction in order to make Python code run faster. JavaScript ES6 modules introduced a similar distinction. Could Python benefit from a formal notion of an "initialization phase"?
45
+
46
+
### **PEP 827 - Type manipulation and annotationlib** — Michael J. Sullivan
47
+
48
+
PEP 827 proposes adding powerful type-level introspection and construction facilities to Python’s type system. This design is inspired largely by TypeScript’s conditional and mapped types, but is heavily adapted to the very different semantics and constraints of Python’s typing model. It will allow typing a wide range of dynamic APIs and metaprogramming that currently are not well typeable.
49
+
50
+
### **Python releases for macOS** — Ned Deily
51
+
52
+
For many years the Python release team has provided Windows and macOS binaries with every Python release. For macOS, how and what we provide has not changed much over the years even though packaging and distribution guidelines and user expectations have. Plus there are now more options available through third-party distributors than in the past.
53
+
54
+
Let's discuss the benefits and costs of providing macOS binary releases going forward as part of a macOS support policy addition to PEP 11 and, based on that, start a discussion of what changes (features, release artifacts, CI / buildbot, core developer and release team commitment) we should be aiming for.
55
+
56
+
### **Spicycrab, the Rust transpiler** — Kushal Das
57
+
58
+
Write typed Python and generate working Rust code via spicycrab. This currently
59
+
includes part of stdlib, async (via tokio), actix-web examples. Slowly more and
60
+
more Rust crates are available as stub typed Python modules, which we can use
61
+
like normal Python code while developing and then compiling the generated Rust
62
+
code as final output. The final goal is to be able to write smaller production code using spicycrab.
63
+
64
+
### **TBC** — Pablo Galindo Salgado
65
+
66
+
TBC
67
+
68
+
### **Thinking about the post era of free-threading Python** — Donghee Na, Tobias Wrigstad, Fridtjof
69
+
70
+
In the free-threading era, Python users will need high-level concurrency primitives that make concurrent programming easier and safer.
71
+
72
+
This session will discuss what kinds of primitives we could provide in the Python standard library, and how to make them feel natural for everyday Python users.
73
+
74
+
75
+
## FAQ
76
+
77
+
### What is the Language Summit?
19
78
20
79
The Python Language Summit is an event for the developers of Python implementations (CPython, PyPy, MicroPython, GraalPython, IronPython, and so on) to share information, discuss our shared problems, and — hopefully — solve them.
21
80
22
81
These issues might be related to the language itself, the standard library, the development process, the status of Python 3.15 (and plans for 3.16), the documentation, packaging, the website, and so forth. The Summit focuses on discussions and consensus-seeking, more than merely on presentations.
23
82
24
-
## Who can attend
83
+
###Who can attend
25
84
26
85
We welcome Python core team and triage team members, active contributors to CPython and alternative Python implementations, and other community members with a topic to discuss with the core team.
27
86
28
-
## Who can propose a discussion topic
87
+
###Who can propose a discussion topic
29
88
30
89
If you have discussion items; seeking consensus; awaiting community feedback on a PEP; need help with your core work; or have specific questions that need answers from the core team, please [submit a proposal](https://forms.gle/nqqc1nMxMjatmD4TA). According to feedback, our audience prefers more discussions and shorter talks.
31
90
@@ -34,37 +93,37 @@ In your proposal, please include the following:
34
93
- why is this topic relevant to the core team;
35
94
- what is needed from the core team out of this topic.
36
95
37
-
## Can I come if I don't sign up?
96
+
###Can I come if I don't sign up?
38
97
39
98
Sorry, no. This is an invite-only event with limited capacity at the venue. After you sign up, we will let you know before 1st June if you're invited.
40
99
41
-
## Do I need to sign up if I’m a Python core team member?
100
+
###Do I need to sign up if I’m a Python core team member?
42
101
43
102
Yes, please! We have limited space, and we want to avoid overcrowding. Please register to reserve your space.
44
103
45
-
## Can I sign up if I’m not a core developer of a Python implementation?
104
+
###Can I sign up if I’m not a core developer of a Python implementation?
46
105
47
106
Yes, you can. In the past, we had quite a number of participants who were not core contributors to CPython or other implementations of Python. Among them were maintainers and representatives from BeeWare, CircuitPython, PyCharm, PSF board members, PyO3 and PyPA.
48
107
49
108
Some of them have since joined the Python core team, so that's a risk you must be willing to accept when signing up.
50
109
51
-
## Do I need to be registered to EuroPython to attend the Language Summit?
110
+
###Do I need to be registered to EuroPython to attend the Language Summit?
52
111
53
112
Yes, this is so that you receive a badge and catering during the day. Any of a Tutorials, Conference, or Combined ticket will do. Core team members can apply for a free ticket via the [Guido van Rossum Core Developer Grant](https://www.europython-society.org/core-grant/). If you only want to attend the Language Summit portion and not the rest of the conference, then we can provide you with a voucher that allows you to be registered at EuroPython. This way you'll be in the system. However, we do recommend that you be registered for the full EuroPython. There are amazing talks and keynotes on the schedule that you wouldn't want to miss.
54
113
55
-
## How can I learn what's happening at the event?
114
+
###How can I learn what's happening at the event?
56
115
57
116
A detailed summary of the event will be published on the [Python Software Foundation blog](https://pyfound.blogspot.com/). Just like last year, the event will be covered by Seth Michael Larson, the Security Developer in Residence at the Python Software Foundation.
58
117
59
-
## Is this event recorded? Can I watch a live stream?
118
+
###Is this event recorded? Can I watch a live stream?
60
119
61
120
No, there will be no recording and no live stream available. If you'd like to participate in discussions, please sign up to attend. If you'd like to listen in, please wait for Seth’s blog posts after the Summit.
62
121
63
-
## I need to ask a private question
122
+
###I need to ask a private question
64
123
65
124
Sure thing! You can message the organizers privately [on Discourse](https://discuss.python.org/) or the core team Discord and we’ll get you sorted.
66
125
67
-
## We hope you have a great event!
126
+
###We hope you have a great event!
68
127
69
128
Your Language Summit cat herding team,<br />
70
129
Emily Morehouse-Valcarcel, Hugo van Kemenade, Lysandros Nikolaou & Łukasz Langa
0 commit comments