"To give you an idea, let's focus on three Python conferences of different sizes on three continents. At PyCon US 2025, 370 new PRs were open to the Python organization during, 286 to the cpython repository alone. Close to 300 PRs were merged into the Python GitHub organization during that time. That's for four days of sprints. This is over 2X the number of PRs handled during the same period when there's no sprint happening."
"There's been two days of sprints at EuroPython in Prague this year, but they didn't disappoint either: 122 new PRs open to the Python organization, including 99 to the cpython repository. 79 PRs were merged into the Python GitHub organization during this time. This is 1.75X the number of PRs handled during a typical weekend. Even single-day sprint days at conferences are pretty productive."
PyCon US 2025 produced 370 new PRs to the Python organization, 286 to cpython, and nearly 300 merges during four days of sprints—over twice the normal PR volume. EuroPython's two-day sprints yielded 122 new PRs (99 to cpython) and 79 merges, about 1.75× typical weekend throughput. A single-day sprint at PyCon Korea produced 59 new PRs (35 to cpython) and over 40 merges, roughly 1.7× usual velocity. Longer sprints amplify contributions because many changes need more than a day to develop, some bugs are stubborn, and features often reveal unexpected complexity when implementation begins. Large coordinated groups accelerate problem solving.
Read at pyfound.blogspot.com
Unable to calculate read time
Collection
[
|
...
]