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 serhiy.storchaka
Recipients asvetlov, giampaolo.rodola, gvanrossum, serhiy.storchaka, vstinner, yselivanov
Date 2017-11-29.10:28:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1511951327.23.0.213398074469.issue32166@psf.upfronthosting.co.za>
In-reply-to
Content
If it is good to drop 3.4 support in the stdlib asyncio, then there is other outdated code.

There is a 3.3 specific workaround in unix_events.py.

There is a 3.4 code or comments in futures.py, sslproto.py, unix_events.py. Maybe comments are related to optional code which can now be used unconditionally.

Note that not all 3.4 code is marked with "Python 3.4". It can be marked with "Python < 3.5".
History
Date User Action Args
2017-11-29 10:28:47serhiy.storchakasetrecipients: + serhiy.storchaka, gvanrossum, vstinner, giampaolo.rodola, asvetlov, yselivanov
2017-11-29 10:28:47serhiy.storchakasetmessageid: <1511951327.23.0.213398074469.issue32166@psf.upfronthosting.co.za>
2017-11-29 10:28:47serhiy.storchakalinkissue32166 messages
2017-11-29 10:28:47serhiy.storchakacreate