Closed saghul closed 11 years ago
Hum, some tests seem to be failing, I'll run the test suite locally...
While attempting to fix the failing tests in test_lookup I think I found a bigger problem underneath:
I lost track of the internals after the big refactor :-) but the changes I'm proposing here are those available in my tornado-pyuv repo, which pass the entire Tornado test suite, so I think there may be some internal problems in gaffer like the one I described above.
More over, I see pyuv handles and the IOLoop used together, which is a bit confusing. Could we just use the Tornado IOLoop for everything? Using the pyuv implementation, that is.
I don't really want to use tornado as the first citizen in gaffer. Imo the ioloop should be just used as a wrapper around pyuv.Loop and then close only handlerslaunched using this ioloop.
I guess in that case the client could receive the ioloop, but i'm worried about what it can imply if later (as I intend to) the client is only based on pyuv (and http-parser). Maybe this isn't a problem?
Ok, got it. In that case I'll modify IOLoop.close not to close all handles in the loop. We can also get rid of the all_fds paramete, because, frankly, when don't you want to close the file descriptors? So IOLoop.close will just close the poll handles it started and the associated file descriptors. This should hopefully do.
Sounds good indeed. Thanks for that :)
Tests pass on OSX, come on Travis, give me some good news!
Tests pass on Travis for 2.7, but building the environment seems to fail for 3.3. Though it's not related to this changes.
Heh, it took longer than expected, but tests also pass on 3.3 :-)
Thanks! Patch looks good for me. I will mege it in some mn.
applied in last head, thanks!
Don't merge yet.