Pythonlings Community Dev Sprint - August 22, 2026

[abhiksark]

Welcome

Pythonlings is hosting a public, beginner-friendly community development sprint on August 22, 2026. The in-person session runs from 11:00 AM to 2:00 PM IST, with online collaboration continuing afterward. The sprint backlog is intentionally split into small, well-scoped work across documentation, curriculum, reliability, CI, the CLI, and the Textual TUI.

Event details

• Date: August 22, 2026
• In-person time: 11:00 AM to 2:00 PM IST
• Location: Amadeus, Electra Block, Prestige Tech Park II, Bengaluru
• Online continuation: The sprint will continue online on the BangPypers Discord after the in-person session. Remote contributors are welcome for the whole sprint — join the Discord and say hello in the thread below.

BangPypers event details and attendance are available on the DevSprint Event Meetup page.

Getting set up

1. Read the contribution guidance and Code of Conduct.
2. Install the project with pip install -e ".[dev]", then run python -m pytest -q before starting.
3. Choose an unassigned sprint issue. You may leave a short coordination note, but issues are not reserved: for in-repository work, the first PR that meets every acceptance criterion and passes its checks is the one considered for merge.
4. Keep each PR focused, explain the user-facing result, and include the verification output requested by its issue.

Collaboration rules

• Ask implementation questions, share discoveries, and celebrate progress in this Discussion.
• Do not create a GitHub Project or promise a release as part of sprint work.
• External-directory work needs extra coordination: leave a preflight comment on the Pythonlings issue, wait for the upstream maintainer to approve the route, and submit only one human-authored PR to each upstream repository.
• Please do not submit a listing where the directory eligibility rules are not met. Research issues record evidence and objective revisit conditions instead.

Help and safety

• General help and design discussion: use this thread.
• Bug reports and feature ideas: use the repository issue forms.
• New exercise ideas: open an Exercise Proposal. These are discussions rather than issues, so anyone can file one without waiting for permissions; a maintainer converts accepted proposals into a scoped issue.
• Security vulnerabilities: follow the private reporting guidance in SECURITY.md; do not disclose them in public issues or this Discussion.

The umbrella tracker links every sprint issue once the backlog is published. Welcome, especially if this is your first open-source contribution!

---

Verified QA backlog

Deep QA of current dev at e1d4dae37234b75124bd6a53f06734296ebbbdee produced 40 new, reproducible, non-duplicate issues. The baseline passed 190 tests, all 292 reference answers, bundled-curriculum verification, strict documentation validation, persistent link checks, and editable plus installed-wheel checks on Python 3.9 through 3.13.

The complete categorized status is in tracker #52.

CLI and core (3)

• #71 cli: reject init --force at the curriculum source
• #72 core: contain invalid UTF-8 exercise files in the runner
• #73 cli: keep status output usable under ASCII locales

TUI (3)

• #74 tui: persist a revert to the originally loaded exercise text
• #75 tui: ignore stale verification results from older edits
• #79 tui: keep key bindings discoverable in narrow terminals

Curriculum (31)

• #80 curriculum: add actionable assertion messages to variables checks
• #81 curriculum: add actionable assertion messages to functions checks (batch 1 of 3)
• #82 curriculum: add actionable assertion messages to functions checks (batch 2 of 3)
• #83 curriculum: add actionable assertion messages to functions checks (batch 3 of 3)
• #84 curriculum: add actionable assertion messages to classes checks (batch 1 of 2)
• #85 curriculum: add actionable assertion messages to classes checks (batch 2 of 2)
• #86 curriculum: add actionable assertion messages to functional checks (batch 1 of 2)
• #87 curriculum: add actionable assertion messages to functional checks (batch 2 of 2)
• #88 curriculum: add actionable assertion messages to decorators checks (batch 1 of 2)
• #89 curriculum: add actionable assertion messages to decorators checks (batch 2 of 2)
• #90 curriculum: add actionable assertion messages to generators checks (batch 1 of 2)
• #91 curriculum: add actionable assertion messages to generators checks (batch 2 of 2)
• #92 curriculum: add actionable assertion messages to context managers checks
• #93 curriculum: add actionable assertion messages to dataclasses checks
• #94 curriculum: add actionable assertion messages to regex checks
• #95 curriculum: add actionable assertion messages to testing checks
• #96 curriculum: add actionable assertion messages to recursion checks (batch 1 of 4)
• #97 curriculum: add actionable assertion messages to recursion checks (batch 2 of 4)
• #98 curriculum: add actionable assertion messages to recursion checks (batch 3 of 4)
• #99 curriculum: add actionable assertion messages to recursion checks (batch 4 of 4)
• #100 curriculum: add actionable assertion messages to itertools checks
• #101 curriculum: add actionable assertion messages to JSON checks (batch 1 of 2)
• #102 curriculum: add actionable assertion messages to JSON checks (batch 2 of 2)
• #103 curriculum: add actionable assertion messages to datetime checks (batch 1 of 2)
• #104 curriculum: add actionable assertion messages to datetime checks (batch 2 of 2)
• #105 curriculum: add actionable assertion messages to enums checks
• #106 curriculum: add actionable assertion messages to pathlib checks
• #107 curriculum: add actionable assertion messages to advanced OOP checks (batch 1 of 2)
• #108 curriculum: add actionable assertion messages to advanced OOP checks (batch 2 of 2)
• #109 curriculum: add actionable assertion messages to async checks (batch 1 of 2)
• #110 curriculum: add actionable assertion messages to async checks (batch 2 of 2)

Documentation (3)

• #76 docs: preserve code structure in generated offline references
• #77 docs: make bundled reference regeneration version-reproducible
• #78 docs: clarify that automatic checks require the built-in editor

Packaging and CI

No new packaging or supported-runtime defect qualified. Source tests and the installed wheel passed on Python 3.9, 3.10, 3.11, 3.12, and 3.13.

Existing issue routing

• The solution-loader documentation finding was added to #39.
• The corrupt-state and .bak behavior was reproduced and added to #45.
• Completed implementation was reconfirmed for fix: make pythonlings update prefer the current workspace #42, fix: preserve existing workspace .gitignore entries #43, and fix: return friendly errors for malformed info.toml files #44, and tracker checkboxes now match their closed state.

Claiming an issue

Choose an open, unassigned issue from tracker #52 and read its exact scope, exclusions, and verification commands. A short coordination comment is welcome, but it is not a reservation. For repository work, the first pull request that satisfies every acceptance criterion and verification requirement is considered for merge.