Author gvanrossum
Recipients gvanrossum, martin.panter, python-dev, rhettinger, serhiy.storchaka, vstinner
Date 2015-03-30.17:45:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJ+vpZd4cHiAda4ybyiiMNtS27QSYZ68h59f04TLejpznw@mail.gmail.com>
In-reply-to <1427737117.77.0.144287373328.issue23326@psf.upfronthosting.co.za>
Content
Yeah, I'd like to see it restored in asyncio. It seems to be just one file
that's currently out of sync with the tulip "upstream" repo.

On Mon, Mar 30, 2015 at 10:38 AM, Serhiy Storchaka <report@bugs.python.org>
wrote:

>
> Serhiy Storchaka added the comment:
>
> Should I restore __ne__ in asyncio? The version without __ne__ will work
> with Python 3.4.3 because issue21408 patch was committed in 3.4 too.
> Explicit __ne__ implementation is just redundant.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue23326>
> _______________________________________
>
History
Date User Action Args
2015-03-30 17:45:23gvanrossumsetrecipients: + gvanrossum, rhettinger, vstinner, python-dev, martin.panter, serhiy.storchaka
2015-03-30 17:45:22gvanrossumlinkissue23326 messages
2015-03-30 17:45:22gvanrossumcreate