Message232783
| Author |
gvanrossum |
| Recipients |
gvanrossum, martin.panter, vstinner, yselivanov |
| Date |
2014年12月17日.00:21:40 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAP7+vJKuLZp2g1qB0mRcCvpKpJE+2yxpHXx1jea74fmoccN_zw@mail.gmail.com> |
| In-reply-to |
<1418775474.65.0.0212569640767.issue23046@psf.upfronthosting.co.za> |
| Content |
Sounds unlikely. If they write "from asyncio.base_events import Server" it
will still work. Only if they wrote "from asyncio.base_events import *"
will they be broken, and that sounds not worth worrying about. So LGTM on
the patch. (But why was Server there at all? Tests?
On Tue, Dec 16, 2014 at 4:17 PM, STINNER Victor <report@bugs.python.org>
wrote:
>
>
> STINNER Victor added the comment:
>
> Here is a patch to expose BaseEventLoop. It removes Server from
> base_events.__all__, which means that "from asyncio.base_events import *"
> will no import Server anymore. Can it break real applications?
>
> ----------
> keywords: +patch
> Added file: http://bugs.python.org/file37475/base_event_loop.patch
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue23046>
> _______________________________________
> |
|