➜

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 christian.heimes
Recipients christian.heimes, eli.bendersky, hroncok, rahul-kumi, scoder, serhiy.storchaka
Date 2020-05-05.09:43:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1588671800.74.0.231443701349.issue36543@roundup.psfhosted.org>
In-reply-to
Content 
3.3.0 was released in 2012. That's almost a lifetime ago. I assume that majority of users either forgot, missed the note, or no longer took the deprecation serious. After seven, eight years we should do our users a service and point out the deprecation with a concrete deadline.
History
Date User Action Args
2020-05-05 09:43:20christian.heimessetrecipients: + christian.heimes, scoder, eli.bendersky, serhiy.storchaka, hroncok, rahul-kumi
2020-05-05 09:43:20christian.heimessetmessageid: <1588671800.74.0.231443701349.issue36543@roundup.psfhosted.org>
2020-05-05 09:43:20christian.heimeslinkissue36543 messages
2020-05-05 09:43:20christian.heimescreate