This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author abartlet
Recipients Anthony Sottile, abartlet, miss-islington, pitrou, serhiy.storchaka, vstinner
Date 2020-03-04.02:01:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1583287285.42.0.817185995397.issue37330@roundup.psfhosted.org>
In-reply-to
Content
I think we are speaking past each other. 

Yes, Python 2 is no longer being changed, which is awesome as we need for fear breakage of the older builds that use that for the build system.

The issue isn't the particular language feature, or that there is no way to further adapt code, but that a valid build script that operates correctly on Python 3.8 will no longer, without warning to us, operate on Python 2.9 or at best 2.10. 

Thankfully the only Samba versions with support for Python3 are still in maintenance, so course I've back-ported patches to the tip of each release branch to work around this change.  But again, that doesn't help when I need to build an arbitrary git revision in the future. 

(That warnings were available, if we knew were to look, is an entirely moot point at this stage).
History
Date User Action Args
2020-03-04 02:01:25abartletsetrecipients: + abartlet, pitrou, vstinner, serhiy.storchaka, Anthony Sottile, miss-islington
2020-03-04 02:01:25abartletsetmessageid: <1583287285.42.0.817185995397.issue37330@roundup.psfhosted.org>
2020-03-04 02:01:25abartletlinkissue37330 messages
2020-03-04 02:01:25abartletcreate