[Python-Dev] Farewell, Python 3.5
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!
___
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/YKZON55BE5JMK6355KPD53HRUXOOYTYN/
Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: [python-committers] Farewell, Python 3.5
Thank you, Larry and the whole release team, for putting so much
work into this !
On 01.10.2020 19:49, Larry Hastings wrote:
>
> 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!
>
>
> ___
> python-committers mailing list -- python-committ...@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committ...@python.org/message/YKZON55BE5JMK6355KPD53HRUXOOYTYN/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Experts (#1, Oct 01 2020)
>>> Python Projects, Coaching and Support ...https://www.egenix.com/
>>> Python Product Development ...https://consulting.egenix.com/
::: We implement business ideas - efficiently in both time and costs :::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
https://www.egenix.com/company/contact/
https://www.malemburg.com/
___
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/JRSWYO3X4JMBG3B6SWI6KWEDUYW5W5SY/
Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Farewell, Python 3.5
Thanks for all of your work, Larry. I really think it was the stability
of these releases that helped push 3.x into dominance over 2.7.
3 version control systems. Insane!
Eric
On 10/1/2020 1:49 PM, Larry Hastings wrote:
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!
___
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/YKZON55BE5JMK6355KPD53HRUXOOYTYN/
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/X3XV5WWYRMXYRDQKMDASSUF7ORCU53X2/
Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Farewell, Python 3.5
Thank you so much Larry, for your wonderful work.
On Thu, Oct 1, 2020 at 8:44 AM Eric V. Smith wrote:
> Thanks for all of your work, Larry. I really think it was the stability of
> these releases that helped push 3.x into dominance over 2.7.
>
> 3 version control systems. Insane!
>
> Eric
> On 10/1/2020 1:49 PM, Larry Hastings wrote:
>
>
> 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!
>
> ___
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to
> python-dev-leave@python.orghttps://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/YKZON55BE5JMK6355KPD53HRUXOOYTYN/
> 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/X3XV5WWYRMXYRDQKMDASSUF7ORCU53X2/
> Code of Conduct: http://python.org/psf/codeofconduct/
>
--
The dead increasingly dominate and strangle both the living and the
not-yet born. Vampiric capital and undead corporate persons abuse
the lives and control the thoughts of homo faber. Ideas, once born,
become abortifacients against new conceptions.
___
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/IXJC7TQ5VISHOCXOAPKXPQUB3Y4P5FBL/
Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Core Dev Sprint: Collecting Discord usernames
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/5016/6), 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-setup-guide. 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 ___ 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/H3BFBA2HH5SQ222DL27YFI3ABKAONAKI/ Code of Conduct: http://python.org/psf/codeofconduct/
