Alyssa Coghlan

+1 from me. I'd suggest looking up where we used to document hg share and adding a similar example for git worktree.

I just set this up myself, and it seems very nice. From my `cpython` dir, it was just a matter of doing: git checkout 3.6 git worktree add ../py36 3.6...

Yeah, it's mainly a matter of explaining that stdlib inclusion comes with significant downsides (such as the increased cognitive burden for future learners, that only being available in future versions...

I'm looking for something a bit more authoritative than that - a way for stdlib maintainers to say "If we say no, consider proposing your idea over here instead". A...

The section on getting set up with the build dependencies would be the right place: https://devguide.python.org/setup/#build-dependencies Since these are mainly useful for Windows (where we can't use the system package...

The other technique I've used is to keep the additional issue open, but have the associated PR be purely a docs change. That was for https://bugs.python.org/issue30661, where changing the default...

Unassigning since I don't want to get in the way of anyone else coming up with improved wording. Beyond that, I agree with Ezio's discussion of why defining this clearly...

A "Task Checklists" section seems potentially plausible to me. However, another way to structure that would be to leave the checklists where they are now, and have the "Task Checklists"...

I think the core dev section may also need to be split, although I'm not sure what the two sub-audiences should be called. The way I think of them: *...

Attempting a more value-neutral description of the two categories: * Procedurally aligned profession: the processes and practices you use in your day job are well-aligned with those used in the...