➜

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 gvanrossum
Recipients gvanrossum, martin.panter, vstinner, yselivanov
Date 2014-12-16.23:51:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJKs5awP6Q6z-9+d1_AXXY1qMHuBuhf7oZ99P_y-YiK-7w@mail.gmail.com>
In-reply-to <1418773512.19.0.835345974183.issue23046@psf.upfronthosting.co.za>
Content 
OK, fine to expose the BaseEventLoop class.

On Tue, Dec 16, 2014 at 3:45 PM, STINNER Victor <report@bugs.python.org>
wrote:
>
>
> STINNER Victor added the comment:
>
> I'm in favor of exposing BaseEventLoop in the asyncio namespace directly
> (asyncio.BaseEventLoop) because I'm using it in various asyncio projects,
> and I don't like having to use submodules. I consider asyncio.base_events
> as the private API.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue23046>
> _______________________________________
>
History
Date User Action Args
2014-12-16 23:51:31gvanrossumsetrecipients: + gvanrossum, vstinner, martin.panter, yselivanov
2014-12-16 23:51:31gvanrossumlinkissue23046 messages
2014-12-16 23:51:31gvanrossumcreate