Hello,
Apparently, Stefan Krah (core developer and author of the C _decimal
module) was silently banned or moderated from posting to python.org
mailing-lists. He asked me to forward the following message:
==================================================================================
Hello,
Today I have left the Python organization. It wasn't an easy decision,
after all there are so many amazing people here.
My vision of how development should be handled differs from many people
who are currently active. Other projects are more aligned with my
preferences, so I prefer to focus my energies elsewhere.
Having a shared understanding of what constitutes politeness is
important and eliminates all sources of friction that sometimes result
in losing one's patience.
All the best,
Stefan Krah
====================================================================================
Best regards
Antoine.
On 10/8/20 4:07 PM, Thomas Wouters wrote:
> Stefan did indeed receive, and was notified of, a 1-year ban from core development.
Thank you for clarifying.
> This action was based on advice from the Conduct WG and our own deliberations. We
> wanted to have a discussion with him before we made this public.
Why would the SC make this one public when they did not make the ban back in June/July
public?
--
~Ethan~
They say being a Python Release Manager is a thankless job, so the Python Secret Underground (PSU), which emphatically does not exist, hereby officially doesn’t thank Larry for his years of diligent service as the Python 3.4 and 3.5 release manager.
On the other hand, the Python Steering Council, Python Software Foundation, and worldwide Python community, all of which emphatically *do* exist, all extend our heartfelt thanks to Larry for his excellent stewardship of Python 3.4 and 3.5!
Python 3.4 and 3.5 were both pivotal releases. While the features of these two releases are too numerous to mention here, they introduced such staples as:
* asyncio
* enum
* pathlib
* async and await keywords
* matrix multiplication operators
* typing and zipapp modules
and so much more. For details, see:
* https://docs.python.org/3/whatsnew/3.4.html
* https://docs.python.org/3/whatsnew/3.5.html
Larry’s first official release of 3.4.0a1 was on 2013-08-03 and his last Python 3.5.10 release was 2020-09-05. That’s 7 years of exemplary release managing!
Larry, from all of us, and from me personally, thank you so much for your invaluable contributions to Python. Enjoy your retirement!
Cheers,
-Barry (on behalf of the PSC and PSF)
Hey all,
The upcoming 2020 Python Core Development Sprint is right around the
corner, and we're currently towards the end of finalizing platform setup.
For using Discord during the sprint on the public Python Discord server (as
voted on in
https://discuss.python.org/t/2020-core-dev-sprint-poll-discord-or-zulip/501…),
we are collecting Discord usernames ahead of time and requesting that all
participants join Python Discord well before the start of the sprint (Oct.
19th). This will allow us to grant all participants a role for joining the
sprint channels (in order to be given the role, participants must be on the
server first).
To send your Discord username, simply reply to this email (without CCing
the list to keep it private) with it included. It is in the format of
"name#0123", and can be seen in the lower left corner of the Discord client
after creating an account (or in "User Settings" > "My Account"). I'll
verify replies against the email address used in the signup form, so please
use the same one if possible.
Prior to joining Python Discord, I recommend checking out the Discord setup
guide that I recently finished:
https://python-core-sprint-2020.readthedocs.io/communication.html#discord-s….
The part on the privacy settings is particularly important for anyone with
a public following to avoid receiving mass DMs and friend requests.
Alternatively, you can join directly at the following perma-link:
https://discord.gg/Q87A9Y9.
As a reminder, potential participants include Python core developers,
triagers, and those in a core dev mentorship. If you haven't already signed
up and are interested in attending, please do so at
https://forms.gle/fhzJdpRHR4GtSRCk9.
Regards,
Kyle Stanley
At last! Python 3.5 has now officially reached its end-of-life. Since
there have been no checkins or PRs since I tagged 3.5.10, 3.5.10 will
stand as the final release in the 3.5 series.
As with a similar announcement I wrote about eighteen months ago, I know
we can all look back fondly on Python 3.5. 3.5 added many new
asynchronous I/O programming features, the "typing" module, and even a
new operator ("@"). Plus many and varied quality-of-life improvements
for the Python programmer, in both the language, the library, the core
implementation, and even the installers. Python 3.5.0 was the best
version of the best language at the time, and since then it's gotten
even better!
My thanks to all the members of the Python 3.5 release team. In
alphabetical order:
Georg Brandl
Julian Palard
Ned Deily
Steve Dower
Terry Reedy
My thanks also to the Python infrastructure team.
The end of Python 3.5 support also ends my tenure as a Python Release
Manager. Congratulations, you survived me and my frequent mistakes!
(Special shouts out to Ned and Benjamin for running around behind the
scenes quietly cleaning up my messes--and not even telling me most of
the time.) Rest assured that I leave you in /much/ better hands with
the current crop of RMs: Ned, Łukasz, and Pablo.
One amusing note. During my tenure as a Python release manager, I had
to deal with /three/ different revision control systems. Although we'd
switched CPython itself to Mercurial by the time 3.4 alpha 0 was
released, there were still many supporting repositories still on
Subversion. (I remember having to do Subversion branch merges as part
of my 3.4 release work... what a pain.) And of course these days we're
on Git (-hub). This straddling of three different workflows certainly
complicated the lives of us Release Managers. So, my friends, please...
make up your minds! ;-)
It's been my honor to serve you,
//arry/
p.s. As of today, every supported version of Python supports f-strings.
The only remaining excuse for "we can't use f-strings" is no longer viable!
