Python Core Sprint 2020¶
Issue Tracker and Discussions: https://github.com/python/core-sprint
For questions and suggestions about the sprint, please open an issue or a discussion item in the core-sprint repo.
For sensitive and private discussions, please get in touch with one of the organizers: Mariatta, Kyle Stanley or Ewa Jodlowska.
The sprint is scheduled for Oct 19 - 23, 2020. This will be an online event instead of the in-person sprint.
The sprint is normally a weeklong (5 work days) sprint, where we would have focus time to work on CPython, finish your PEPs, review pull requests, etc.
All core devs, Python triage members, and active core dev mentees are invited to participate.
Sign up form: https://forms.gle/84NkyYt5g616fs1r5
After signing up through the form, please add yourself to this doc by creating a pull request. You’ll want to add yourself to Participant List, Sprint Projects, and if applicable Python community Q&A session.
Help improve this documentation by opening an issue or creating a pull request at https://github.com/python/core-sprint
Contents:
- Code of Conduct
- Schedule
- Participant List
- Sprint Projects
- Sprint Blog Post
- C-API/runtime/subinterpreters
- stdlib modules
- Parser improvements
- Core workflow
- General issue triage/ PR reviews
- Release management
- Typing
- asyncio
- GC improvements
- Optimize startup time
- Buildbot Configuration
- Deprecate old modules
- F-strings
- Dataclasses
- Language Design Discussions
- Windows
- MacOS
- DSLs and support for dynamic and/or annotated ASTs
- Performance improvements
- Increasing new contributors; mentorship
- importlib.resources
- multiphase init and heap type
- Documentation
- PEP 447
- Security / SSL
- Gilectomy
- New PEP
- Posix subprocess
- Build System
- PEP 622/634 Structural Pattern Matching
- Wheel interpreter naming for 3.10
- Hypothesis standard library tests
- Auto-Formatting the CPython Codebase
- Communication
- Discord Setup Guide
- Python community Q&A session
- Social Activities
- Tech check session/tech day