[Python-Dev] Re: Where it is decided whether "lib" or "lib64" ends up in sys.path on a POSIX (non MacOS) system?

[Victor Stinner]

FYI Python 3.9 has a new sys.platlibdir to choose between "lib" and
"lib64". Fedora and OpenSUSE use /usr/lib64 directory on 64-bit
systems rather than /usr/lib.

On 64-bit Fedora, sys.platlibdir is set to lib64:

$ python3.9 -c 'import sys; print(sys.platlibdir)'
lib64

Commented (simplified) sys.path:

$ python3.9 -m site
sys.path = [
(...)
'/usr/lib64/python3.9',  # stdlib (pure Python)
'/usr/lib64/python3.9/lib-dynload',  # stdlib (C extensions)
(...)
'/usr/lib64/python3.9/site-packages',
'/usr/lib/python3.9/site-packages',  # RPM packages installed by dnf
]
(...)

Fedora also uses sub-directories in /usr/local for packages installed
by pip (here are directories of Python 3.8):

'/usr/local/lib64/python3.8/site-packages',
'/usr/local/lib/python3.8/site-packages',

For curious people, see https://bugs.python.org/issue1294959 which
took 15 years to be fixed! Fedora and OpenSUSE maintained a large
downstream stream for at least 10 years :-) I added sys.platlibdir to
remove this downstream change.

Victor

Le sam. 3 oct. 2020 à 16:46, Mikhail Golubev via Python-Dev
 a écrit :
>
> Hi everyone!
>
> First of all, sorry for bringing up, perhaps, a trivial matter, but since 
> it's about the sources I guess it's better to ask it here.
>
> I'm investigating a curious problem caused by the fact that in a user's 
> virtualenv, created with the standard "venv" module, "lib64" directory, 
> traditionally symlinked to "lib", gets included in sys.path
> instead of "lib" itself.
>
> ```
> $ python -msite
>
> sys.path = [
> '/current/working/directory'
> '/usr/lib64/python36.zip',
> '/usr/lib64/python3.6',
> '/usr/lib64/python3.6/lib-dynload',
> '/path/to/venv/lib64/python3.6/site-packages',
> ]
> ```
>
> The user is on Gentoo, and, though the venv's layout is exactly the same, 
> it's different from the typical result on a Debian-based distribution where 
> it's the original "lib" in sys.path, not its "lib64" link. I'm wondering 
> what's controlling this behavior. Modules/getpath.c doesn't mention 
> architecture-dependent lib directories anywhere, at least at first glance. 
> Could someone please give me a hint about where to look in the sources or, 
> maybe, which build options are affecting this?
>
> Thanks a lot!
> ___
> 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/5T72JDQG7D44CFYN7URPB5I5JATMD6AR/
> Code of Conduct: http://python.org/psf/codeofconduct/



-- 
Night gathers, and now my watch begins. It shall not end until my death.
___
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/OBKWLJPJLONT4TV6YIQM5N2JJBCX4VMR/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: PR checks hang because travis does not report back to github

[Victor Stinner]

Hi,

Would you mind reporting the issue to
https://github.com/python/core-workflow/issues so we can aggregate
information about this issue?

Latest changes related to Travis CI.

Travis CI migrated from legacy API to new GitHub Action API:
https://github.com/python/core-workflow/issues/371

Removal of old webhooks:
https://github.com/python/core-workflow/issues/374

Travis CI can be reported/discussed at:
https://travis-ci.community/

--

If Travis CI is made optional (not mandatory), can we mark another
Linux CI as mandatory? Like the "GitHub Action Ubuntu" job? I didn't
pay attention to whether it's reliable or not.

In my experience, no CI is reliable, and all CI need attention from
time to time :-)

Victor

Le dim. 4 oct. 2020 à 19:46, Stefan Behnel  a écrit :
>
> Hi devs,
>
> I have a trivial documentation PR
>
> https://github.com/python/cpython/pull/22464
>
> for which travis (unsurprisingly) had a successful run,
>
> https://travis-ci.com/github/python/cpython/builds/187435578
>
> but github lists the travis build as "created" instead of "passed".
>
> https://github.com/python/cpython/pull/22464/checks?check_run_id=1188595760
>
> I already tried closing the PR and reopening it, and also triggering the
> build again on travis side, but github still fails to pick up the build 
> status.
>
> I tried creating a new PR, but it seems that github (or travis) deduplicate
> the build requests and still refer to the original build, so that there is
> still no response from travis.
>
> I also cannot find a way to terminate the checks process in github, or
> otherwise make it stop waiting for Godot.
>
> Is this a known issue? Is there anything I can do about it?
>
> Thanks,
> Stefan
> ___
> 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/4TNKVOJ2LUJZZHHIBNORZ7GIVMYMNDER/
> Code of Conduct: http://python.org/psf/codeofconduct/



-- 
Night gathers, and now my watch begins. It shall not end until my death.
___
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/IAQSNBCMBA65YQSZ75DH3WJPLM3MHTYI/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Where it is decided whether "lib" or "lib64" ends up in sys.path on a POSIX (non MacOS) system?

[Mikhail Golubev via Python-Dev]

Oh, wow. Thanks for all the insights! Since there just wasn't a standard
solution for that in the form of sys.platlibdir before 3.9, I guess I
should better check the downstream version of CPython sources used by
Gentoo directly. The fact that Fedora and OpenSUSE use the same layout is
also very helpful.

On Mon, Oct 5, 2020 at 11:57 AM Victor Stinner  wrote:

> FYI Python 3.9 has a new sys.platlibdir to choose between "lib" and
> "lib64". Fedora and OpenSUSE use /usr/lib64 directory on 64-bit
> systems rather than /usr/lib.
>
> On 64-bit Fedora, sys.platlibdir is set to lib64:
>
> $ python3.9 -c 'import sys; print(sys.platlibdir)'
> lib64
>
> Commented (simplified) sys.path:
>
> $ python3.9 -m site
> sys.path = [
> (...)
> '/usr/lib64/python3.9',  # stdlib (pure Python)
> '/usr/lib64/python3.9/lib-dynload',  # stdlib (C extensions)
> (...)
> '/usr/lib64/python3.9/site-packages',
> '/usr/lib/python3.9/site-packages',  # RPM packages installed by dnf
> ]
> (...)
>
> Fedora also uses sub-directories in /usr/local for packages installed
> by pip (here are directories of Python 3.8):
>
> '/usr/local/lib64/python3.8/site-packages',
> '/usr/local/lib/python3.8/site-packages',
>
> For curious people, see https://bugs.python.org/issue1294959 which
> took 15 years to be fixed! Fedora and OpenSUSE maintained a large
> downstream stream for at least 10 years :-) I added sys.platlibdir to
> remove this downstream change.
>
> Victor
>
> Le sam. 3 oct. 2020 à 16:46, Mikhail Golubev via Python-Dev
>  a écrit :
> >
> > Hi everyone!
> >
> > First of all, sorry for bringing up, perhaps, a trivial matter, but
> since it's about the sources I guess it's better to ask it here.
> >
> > I'm investigating a curious problem caused by the fact that in a user's
> virtualenv, created with the standard "venv" module, "lib64" directory,
> traditionally symlinked to "lib", gets included in sys.path
> > instead of "lib" itself.
> >
> > ```
> > $ python -msite
> >
> > sys.path = [
> > '/current/working/directory'
> > '/usr/lib64/python36.zip',
> > '/usr/lib64/python3.6',
> > '/usr/lib64/python3.6/lib-dynload',
> > '/path/to/venv/lib64/python3.6/site-packages',
> > ]
> > ```
> >
> > The user is on Gentoo, and, though the venv's layout is exactly the
> same, it's different from the typical result on a Debian-based distribution
> where it's the original "lib" in sys.path, not its "lib64" link. I'm
> wondering what's controlling this behavior. Modules/getpath.c doesn't
> mention architecture-dependent lib directories anywhere, at least at first
> glance. Could someone please give me a hint about where to look in the
> sources or, maybe, which build options are affecting this?
> >
> > Thanks a lot!
> > ___
> > 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/5T72JDQG7D44CFYN7URPB5I5JATMD6AR/
> > Code of Conduct: http://python.org/psf/codeofconduct/
>
>
>
> --
> Night gathers, and now my watch begins. It shall not end until my death.
>


-- 
Mikhail Golubev
Software Developer
JetBrains
http://www.jetbrains.com
The drive to develop
___
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/4OWDUJM4346POVNS6Y4KBHJ5WVKGLWUR/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: PR checks hang because travis does not report back to github

[Stefan Behnel]

Ned Deily schrieb am 05.10.20 um 01:19:
> On Oct 4, 2020, at 15:55, Terry Reedy wrote:
>>
>> On 10/4/2020 2:32 PM, Mariatta wrote:
>>> This is a known issue and I have brought it up in GitHub OS Maintainers 
>>> Feedback Group. It happens to other projects as well.
>>> Currently we have branch protection rule where even administrators couldnt 
>>> merge the PR unless all the required checks passed.
>>> Perhaps we can relax the rule to allow administrators to merge the stuck 
>>> PRs. At least temporarily until Travis/GitHub fixes it. Does this sound 
>>> okay?
>>
>> If we are told how to ping the admins, it would be better than being stuck.
> 
> If you run into a problem like this with a stuck PR, contact the release 
> manager for the branch directly via email. Release managers can override the 
> restrictions and we don't always read every list immediately.
> 
> Because this was a trivial change and because of time zones, I've taken the 
> liberty of acting in Pablo's behalf: it's now merged. 

Thank you Ned, and good to know.

Stefan
___
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/P7HPR3BSG7BO3I7562VULK64ZROGOZT2/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Thank you Larry Hastings!

[Barry Warsaw]

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)



signature.asc
Description: Message signed with OpenPGP
___
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/QGIHFU64TBYT56K6M5A5LYTYTSVFKHWQ/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Thank you Larry Hastings!

[Oz Tiram]

Thank you ☺️.
This is what makes python great.



On Mon, Oct 5, 2020, 20:41 Barry Warsaw  wrote:

> 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)
>
> ___
> 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/QGIHFU64TBYT56K6M5A5LYTYTSVFKHWQ/
> 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/HHNWLWP7IPL2APS4L2BWFTWGYJCD6HJJ/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Thank you Larry Hastings!

[Guido van Rossum]

Thank you Larry!

On Mon, Oct 5, 2020 at 11:39 AM Barry Warsaw  wrote:

> 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)
>
> ___
> 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/QGIHFU64TBYT56K6M5A5LYTYTSVFKHWQ/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>


-- 
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here?)*

___
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/5BQHPUAVD2CVLUEF3S32HHLL5GYZ2BLY/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Thank you Larry Hastings!

[Tal Einat]

On Mon, Oct 5, 2020 at 9:39 PM Barry Warsaw  wrote:
>
> 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)

These praises are certainly very well deserved!

You have my thanks as well, Larry.
- Tal Einat
___
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/SZVPDOXQA4KL7NUHB4CLLFLHL37BLQ22/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Thank you Larry Hastings!

[Simon Cross]

Yay! Thanks Larry!

And they were two of the releases which really helped Python 3 take off. :D
___
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/U3M5RTYDUTQGHTCZZ3UZPLPNB3DZAEWN/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Thank you Larry Hastings!

[Hasan Diwan]

Thanks, Mr Hastings! -- H
-- 
OpenPGP:
https://sks-keyservers.net/pks/lookup?op=get&search=0xFEBAD7FFD041BBA1
If you wish to request my time, please do so using
*bit.ly/hd1AppointmentRequest
*.
Si vous voudrais faire connnaisance, allez a *bit.ly/hd1AppointmentRequest
*.

Sent
from my mobile device
Envoye de mon portable
___
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/7FLWTS362WJK66UPTT2242PSOF2PADRG/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] [RELEASE] Python 3.9.0 is now available, and you can already test 3.10.0a1!

[Łukasz Langa]

On behalf of the Python development community and the Python 3.9 release team, 
I’m pleased to announce the availability of Python 3.9.0.

Python 3.9.0 is the newest feature release of the Python language, and it 
contains many new features and optimizations. You can find Python 3.9.0 here:

https://www.python.org/downloads/release/python-390/ 


Most third-party distributors of Python should be making 3.9.0 packages 
available soon.

See the “What’s New in Python 3.9 
” document for more 
information about features included in the 3.9 series. Detailed information 
about all changes made in 3.9.0 can be found in its change log 
.

Maintenance releases for the 3.9 series will follow at regular bi-monthly 
intervals starting in late November of 2020.



OK, boring! Where is Python 4?

Not so fast! The next release after 3.9 will be 3.10. It will be an incremental 
improvement over 3.9, just as 3.9 was over 3.8, and so on.

In fact, our newest Release Manager, Pablo Galindo Salgado, prepared the first 
alpha release of what will become 3.10.0 a year from now. You can check it out 
here:

https://www.python.org/downloads/release/python-3100a1/ 


We hope you enjoy the new releases!

Thanks to all of the many volunteers who help make Python Development and these 
releases possible! Please consider supporting our efforts by volunteering 
yourself or through organization contributions to the Python Software 
Foundation.

https://www.python.org/psf/ 
More resources

Online Documentation 
PEP 596 , 3.9 Release Schedule
PEP 619 , 3.10 Release Schedule
Report bugs at https://bugs.python.org .
Help fund Python and its community .
Your friendly release team,
Ned Deily @nad 
Steve Dower @steve.dower 
Pablo Galindo Salgado @pablogsal 
Łukasz Langa @ambv ___
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/ZSQOHQYBEZV3DUZPDXCI4QWWZJI2KVXE/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Thank you Larry Hastings!

[Łukasz Langa]

> On 5 Oct 2020, at 20:38, Barry Warsaw  wrote:
> 
> Larry, from all of us, and from me personally, thank you so much for your 
> invaluable contributions to Python.

Yes, definitely! Thank you.


> Enjoy your retirement!

Not so fast! Now you have all that extra free time to return to the Gilectomy! 🤓

- Ł
___
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/T4OEUJWMSKXC4GJ5UY3ZECWFI5PYFWVP/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Thank you Larry Hastings!

[Mariatta]

Thank you, Larry!

On Mon, Oct 5, 2020, 11:39 AM Barry Warsaw  wrote:

> 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)
>
> ___
> 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/QGIHFU64TBYT56K6M5A5LYTYTSVFKHWQ/
> Code of Conduct: https://www.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/5MKEFZFX3CA5DZL3AYOWJ7W7RCJMFIJC/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Thank you Larry Hastings!

[Pablo Galindo Salgado]

As someone that went through doing a release just now and now what it
entailsthanks a lot for all the work, Larry! :)

On Mon, 5 Oct 2020 at 19:39, Barry Warsaw  wrote:

> 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)
>
> ___
> 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/QGIHFU64TBYT56K6M5A5LYTYTSVFKHWQ/
> Code of Conduct: https://www.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/JDQMPPBGVKKUR5CWUANYAAYU3EQPFR42/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Thank you Larry Hastings!

[Brian Ray]

Well done Larry! so long and thanks for all the Pythons.

-- 
Brian Ray
brian-ray.me

ᐧ
___
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/QBNSLYLN534JDHIC26KKSKNKPGGT7MEG/
Code of Conduct: http://python.org/psf/codeofconduct/