> On 9 Aug 2016, at 18:35, Brett Cannon <br...@python.org> wrote:
>
>> Necessarily, if you can test it with tests that don’t involve writing mocks
>> for anything in the socket, select, selectors, or asyncio modules, you’re
>> probably in a pretty good place to be arguing that you’re I/O free. If your
>> tests only use the public interfaces, then you’re totally set.
>
> Which "public interfaces" are you referring to? For me, any I/O-free library
> shouldn't be driving the I/O, just a producer/consumer of data. That means
> even if something follows e.g. the public interface of a socket that it
> wouldn't qualify as that suggests the library gets to make the call on when
> the I/O occurs and that you expose a socket for it to use.
Sorry, I just meant the public API of the no-I/O library.
Cory
_______________________________________________
Async-sig mailing list
Async-sig@python.org
https://mail.python.org/mailman/listinfo/async-sig
Code of Conduct: https://www.python.org/psf/codeofconduct/
