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
{{ message }}
Repository navigation
Commit c2f56ff
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: content/posts/language-summit-2026-developer-in-residence-update-and-future/index.md
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,13 @@ Petr started the discussion by listing the responsibilities in his contract:
21
21
* Regularly reporting on this work to the Steering Council and the wider community.
22
22
* Additional responsibilities as directed.
23
23
24
+
<figure>
25
+
26
+
27
+
28
+
<figcaption>Photo by Hugo van Kemenade, licensed <ahref="https://creativecommons.org/licenses/by-nc-sa/4.0/deed.en">CC BY-NC-SA 4.0</a>.</figcaption>
29
+
</figure>
30
+
24
31
Referencing the explicit “Responding to requests for assistance from core developers”, Petr noted that there “haven’t been that many requests for assistance” recently, so he wanted to ask core developers to communicate what they might want done, either at the Language Summit or later.
25
32
26
33
Petr continued with an update on what he’d accomplished from 2024 to 2026, including maintaining [buildbots](https://devguide.python.org/testing/buildbots/), mentoring multiple people into becoming triagers or core developers, working on the [Stable ABI](https://docs.python.org/3/c-api/stable.html) for [free-threaded Python](https://docs.python.org/3/howto/free-threading-python.html), working on security vulnerability fixes, and managing CPython sprints at conferences. He compared this work to what Łukasz had accomplished in his five years of tenure, which included more “large-scale project management”, organizing events like the Language Summit, talking to sponsors, and overseeing the other Python Developers-in-Residence.
@@ -36,7 +43,16 @@ Petr summarized his approach to the role as focusing on “important tasks, but
36
43
Former Developer-in-Residence Łukasz Langa chimed in with a problem he and other core developers had noticed: the large volume of (likely) LLM-generated pull requests being submitted to CPython. One of Łukasz’s early goals for CPython [when he joined as Developer-in-Residence](https://lukasz.langa.pl/a072a74b-19d7-41ff-a294-e6b1319fdb6e/) was “addressing the PR backlog”, which was successful for some time, but that progress has now completely reversed with LLMs. Łukasz suggested either triaging these PRs somehow, noting he wasn’t sure “how many full-time jobs that task is”, or coming up with “some systematic solution”.
37
44
Petr confirmed triaging every LLM pull request wasn’t something he wanted to do, but he was “hired to also do tasks he didn’t want to do”.
38
45
39
-
There was some discussion between Stefan Behnel and Mark Shannon about ensuring some amount of review “before a human looks at a pull request”, such as having an LLM provide a first pass on a pull request. Savannah Ostrowski was hesitant to engage with drive-by LLM contributions: “I’m not willing to give away my time because it won’t change their behavior”. She suggested that other core developers “nope out” if they didn’t want to engage.
46
+
There was some discussion between Stefan Behnel and Mark Shannon about ensuring some amount of review “before a human looks at a pull request”, such as having an LLM provide a first pass on a pull request.
47
+
48
+
<figure>
49
+
50
+
51
+
52
+
<figcaption>Photo by Hugo van Kemenade, licensed <ahref="https://creativecommons.org/licenses/by-nc-sa/4.0/deed.en">CC BY-NC-SA 4.0</a>.</figcaption>
53
+
</figure>
54
+
55
+
Savannah Ostrowski was hesitant to engage with drive-by LLM contributions: “I’m not willing to give away my time because it won’t change their behavior”. She suggested that other core developers “nope out” if they didn’t want to engage.
40
56
41
57
Mark Shannon recommended everyone [watch Pablo Galindo Salgado’s keynote on this topic](https://www.youtube.com/watch?v=e8uozuvRf7g).
42
58
There is also a Language Summit Lightning Talk by Gregory P. Smith and Łukasz Langa about attempting to
Copy file name to clipboardExpand all lines: content/posts/language-summit-2026-namespaces/index.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,14 @@ published: true
9
9
10
10
Steering Council member and Release Manager Pablo Galindo Salgado opened the Language Summit this year to propose solutions to a problem that everyone who’s used Python has encountered at least once before.
11
11
12
+
<figure>
13
+
14
+
15
+
16
+
<figcaption>Photo by <ahref="https://www.flickr.com/photos/europython/55514508261/">EuroPython</a>, licensed <ahref="https://creativecommons.org/licenses/by-nc-sa/4.0/">CC BY-NC-SA 4.0</a>.</figcaption>
17
+
</figure>
18
+
19
+
12
20
The issue manifests as seemingly random `AttributeError` exceptions from modules like `json`, `math`, or `http` for names you know are correct. Why is the standard library suddenly raising errors?
13
21
14
22
$ cat game.py
@@ -70,6 +78,13 @@ ImportError
70
78
# But new modules without 'std.' wouldn't work...
71
79
```
72
80
81
+
<figure>
82
+
83
+
84
+
85
+
<figcaption>Photo by <ahref="https://www.flickr.com/photos/europython/55514668529/">EuroPython</a>, licensed <ahref="https://creativecommons.org/licenses/by-nc-sa/4.0/">CC BY-NC-SA 4.0</a>.</figcaption>
86
+
</figure>
87
+
73
88
Python wouldn’t be alone, either. Many other programming languages have
74
89
already namespaced their standard library (or equivalent):
75
90
@@ -116,6 +131,13 @@ Guido van Rossum asked whether every stdlib module would eventually need to move
116
131
117
132
Peter Bierma asked whether the new `std` namespace would add performance costs, to which Pablo answered that the cost would be “effectively zero”.
118
133
134
+
<figure>
135
+
136
+
137
+
138
+
<figcaption>Photo by Hugo van Kemenade, licensed <ahref="https://creativecommons.org/licenses/by-nc-sa/4.0/deed.en">CC BY-NC-SA 4.0</a>.</figcaption>
139
+
</figure>
140
+
119
141
Thomas Wouters imagined an incremental rollout of the new `std` namespace, proposing that new modules would land under the `std` namespace, with the possibility of a future mode that disables top-level shadowing entirely once enough of the ecosystem has moved.
120
142
121
143
Stefan Behnel felt that Python “should provide a way to confidently import from the standard library”. He offered a potential solution that would keep most code the same: limiting the proposal to `from` imports. The syntax would be `from std import random`, so the module name would be the same and the `std` namespace wouldn’t appear in user code. This would also avoid the issue of [`sys.modules`](https://docs.python.org/3/library/sys.html#sys.modules) duplicating the module. Guido concurred, noting that `from std` could be magic. A “special keyword”, Pablo added.
0 commit comments