[Python-Dev] PEP 607: Shared background for PEPs 602 and 605
Hi folks, Since we have two competing proposals for the Steering Council to consider when it comes to the target release date for Python 3.9.0, Steve, Łukasz and I put together a short-ish overview of the common set of problems that the two PEPs are both attempting to address, as well as the common risks that they're attempting to mitigate. If folks have questions or suggestions regarding the specific proposals, those discussion threads can be found on Discourse here: PEP 602 (12 month release cadence): https://discuss.python.org/t/pep-602-annual-release-cycle-for-python/2296 PEP 605 (24 month traditional release cadence with a rolling pre-release stream): https://discuss.python.org/t/pep-605-a-rolling-feature-release-stream-for-cpython/2418 There's also a thread for the new overview PEP: https://discuss.python.org/t/pep-607-shared-background-for-the-release-cadence-peps/2528 I expect most comments will be best targeted at the threads for the specific proposals, but the PEP 607 thread should still be useful if folks have questions or comments about the overview PEP itself. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/YVSOOFLCBHPIA3HBL4L2BFBJENVHZDJC/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] EnHackathon 2019 - seeking core dev support
Hi all, In early November this year I'll be leading the first ever Python 'EnHackathon' at the Ensoft Cisco office - we anticipate having ~10 first-time contributors, all with experience writing C and/or Python (and training in both). We each have up to 5 days (per year) to contribute, with my intention being to focus on contributing to CPython. We will be blogging about our experience (probably using GitHub pages) - I'll send out the URL when it's been set up. Having spoken to people about this at PyCon UK this year and emailed on the core-mentorship mailing list, I'm posting here looking for any core devs who would be happy to provide us with some guidance. I'm wary of PR reviews being a blocker, and not wanting my co-contributors to feel disheartened by issues they're working on not reaching a resolution. We're open to working on almost any area of CPython, although particular areas of interest/familiarity might be: CPython core, re, unittest, subprocess, asyncio, ctypes, typing. There would be scope for us to work in small teams to work on more substantial issues if that is seen as a useful way to contribute, otherwise we can start with some of the easier issues on bpo. Would anyone here be willing to offer some support to help us reach our full potential? Please don't hesitate to contact me if you're interested in any way, or if you have any advice. If this year is a success there's a high probability we would look to do a similar thing in future years (with the experience from this year already in the bag)! Thanks, Lewis ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/Y6BVYZZVOE27YC24ZXELYBVGDGDB523V/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: EnHackathon 2019 - seeking core dev support
Hi Lewis. I'm a trigger (not a core developer), but I'd be happy to make myself available during that time for expedited PR reviews. Ideally, the core review / merge stage would be your only bottleneck then. I'm a bit busy next month though, so do you know the actual dates / time / time zones you plan to be working in? Also, are there any specific issues you have identified that you want to work on within your stated areas of interest? If so, I can do some homework before in order to speed up the reviews. I'd recommend that all PR authors review the contributing section of the developers guide beforehand: https://devguide.python.org/pullrequest Specifically, make sure that every contributor has signed the CLA at least a couple of business days before (it's often the longest blocker for first-time contributions): https://devguide.python.org/pullrequest/#licensing Looking forward to your help! Brandt ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/5GMVGDLVCTP67VFMUBQDLWNNP22EADAU/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: EnHackathon 2019 - seeking core dev support
Hi Brandt, Thanks a lot for offering to help out! Hopefully will also be a couple of core devs happy to help in November to avoid bottlenecks as much as possible. We'll be working between the hours of 10am-6pm UK time. Dates are TBC and can partly be flexible around when people like yourself are available. We still need to do some more work to identify candidate issues, but I'll let you know when we've done so (any suggestions from anyone are welcome!). I'll also make sure everyone is compliant with the standard requirements to get a PR merged. Thanks, Lewis On Sun, 20 Oct 2019, 16:25 Brandt Bucher, wrote: > Hi Lewis. > > I'm a trigger (not a core developer), but I'd be happy to make myself > available during that time for expedited PR reviews. Ideally, the core > review / merge stage would be your only bottleneck then. > > I'm a bit busy next month though, so do you know the actual dates / time / > time zones you plan to be working in? Also, are there any specific issues > you have identified that you want to work on within your stated areas of > interest? If so, I can do some homework before in order to speed up the > reviews. > > I'd recommend that all PR authors review the contributing section of the > developers guide beforehand: > https://devguide.python.org/pullrequest > > Specifically, make sure that every contributor has signed the CLA at least > a couple of business days before (it's often the longest blocker for > first-time contributions): > https://devguide.python.org/pullrequest/#licensing > > Looking forward to your help! > > Brandt > ___ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/5GMVGDLVCTP67VFMUBQDLWNNP22EADAU/ > Code of Conduct: http://python.org/psf/codeofconduct/ > ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/PAM6DR5HTWRBXJOBGUVKOCFPF5C3A5YS/ Code of Conduct: http://python.org/psf/codeofconduct/
