Author rhettinger
Recipients barry, brett.cannon, dstufft, eric.smith, gvanrossum, r.david.murray, rhettinger, vstinner
Date 2015-09-08.03:33:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441683190.99.0.579508275287.issue25002@psf.upfronthosting.co.za>
In-reply-to
Content
> Now that we've got asyncio in two releases (3.4 and 3.5) 
> we should start deprecating asyncore and asynchat.

If we care about making it easier for organizations to move from Python 2 to Python 3, we should develop a strong aversion to deprecating modules that have been around for a long time and aren't broken.

In addition, we should give weight and support to the numerous projects that are trying to have a code base the runs in both Python 2 and Python 3 (hence the astonishing success of the six module). 

Already my tooling for testing Python 3.6 is broken because some core dev aggressively removed functions from the inspect module that were deprecated in favor of using Signature objects.  That broke the popular Hypothesis testing tool which was carefully written to work for both Python 2 and Python 3.  In order to work again that tool will have to be modified to copy in the old code that was just taken out.

don't-leave-your-users-behind-ly yours ...
History
Date User Action Args
2015-09-08 03:33:11rhettingersetrecipients: + rhettinger, gvanrossum, barry, brett.cannon, vstinner, eric.smith, r.david.murray, dstufft
2015-09-08 03:33:10rhettingersetmessageid: <1441683190.99.0.579508275287.issue25002@psf.upfronthosting.co.za>
2015-09-08 03:33:10rhettingerlinkissue25002 messages
2015-09-08 03:33:10rhettingercreate