This is a good point. It made more sense in the early days when I wanted to avoid importing modules that you don't need. But __init__.py imports them all anyways. So go ahead and change this in the tests.
(However, inside the asyncio package, please don't use "import asyncio" -- recursive imports cause all kinds of things to break even if it seems to work find when you try it.) On Thu, Jan 23, 2014 at 3:25 AM, Victor Stinner <[email protected]> wrote: > Hi, > > I don't understand why Tulip unit tests import submodules instead of > using the public API. Example: "from asyncio import tasks" and then > use "tasks.Task()". > > What do you think of only importing asyncio and use the asyncio module > instead? > > It would ensure that all required symbols are exported. For example, > SubprocessTransport was not exported in a previous version. > > Victor -- --Guido van Rossum (python.org/~guido)
