Raymond Hettinger added the comment:

> 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 ...

----------
nosy: +rhettinger

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25002>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to