To recognize the good contributions of Sanyam Khurana, I gave him the
bug triage permission on bugs.python.org. (In practice, Ezio gave him
He already commited 9 changes into the master branch since April, 2017.
2017-12-06 23:07 GMT+01:00 Cheryl Sabella <cheryl.sabella(a)gmail.com>:
> Wow, this is a shock!
I'm sorry, maybe I had to warn you before? ;-)
> Thank you, Victor, Ezio, and everyone else. This is
> such an amazing and welcoming community, so thank you for letting me be a
> part of it.
Thanks for your continued contributions!
On Dec 6, 2017 9:43 AM, "Victor Stinner" <victor.stinner(a)gmail.com> wrote:
To recognize the good contributions of Cheryl Sabella, I gave her the
bug triage permission on bugs.python.org. (In practice, Ezio gave her
In the past, such "promotion" wasn't always advertized on
python-committers, but my intent is to make our process more
transparent and award people who deserve it!
IMHO bug triage is the first step/milestone to become a core developer
in the long term.
FYI She pushed not less than 14 commits into the master branch since
python-committers mailing list
Code of Conduct: https://www.python.org/psf/codeofconduct/
Announcing the immediate availability of Python 3.6.4 release candidate 1
and of Python 3.7.0 alpha 3!
Python 3.6.4rc1 is the first release candidate for Python 3.6.4, the next
maintenance release of Python 3.6. While 3.6.4rc1 is a preview release and,
thus, not intended for production environments, we encourage you to explore
it and provide feedback via the Python bug tracker (https://bugs.python.org).
3.6.4 is planned for final release on 2017-12-18 with the next maintenance
release expected to follow in about 3 months. You can find Python 3.6.4rc1
and more information here:
Python 3.7.0a3 is the third of four planned alpha releases of Python 3.7,
the next feature release of Python. During the alpha phase, Python 3.7
remains under heavy development: additional features will be added
and existing features may be modified or deleted. Please keep in mind
that this is a preview release and its use is not recommended for
production environments. The next preview release, 3.7.0a4, is planned
for 2018-01-08. You can find Python 3.7.0a3 and more information here:
nad(a)python.org -- 
Back when we were deciding between GitHub and GitLab, we created this project:
Unless anyone objects, we’re going to delete this project. We have no need for this now that CPython development is on GitHub.
(No, we’re not getting rid of the group, just the project.)
Congratulations to the owners of the newly accepted PEPs. The code cutoff for 3.7.0 alpha 3 is scheduled for today (along with 3.6.3rc1). I know at least one of the PEPs has code ready to commit. I will hold off on tagging 3.7.0a3 for another 6 hours or so. If you feel your code is adequately reviewed and ready to go, go for it; likewise for normal bug fixes and doc changes. But keep in the mind that there is still one more alpha preview release coming prior to the beta 1 feature code freeze, so no need to panic.
nad(a)python.org -- 
Just a heads up that I'll be mostly offline for the last 3 weeks of December.
I don't think there's anything in particular coming up that will need
my attention specifically (I'm hoping we can get the
DeprecationWarning PEP resolved this week), but it does mean I won't
be around to review startup refactoring or subinterpreter related PRs
if any further work is done on those.
P.S. I'd still like to get PEP 558's "Defined semantics for locals()"
included in 3.7, but I'm also OK with it slipping to 3.8 - the quirky
behaviour that it addresses has been around for a decade and a half,
so I don't think anyone is really going to care all that much whether
it gets fixed in 2018 or in 2019.
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia