vector57

I will briefly plug my library `unsync` (https://github.com/alex-sherman/unsync#quick-overview) which wraps all these methods (multiprocessing/threading/asyncio) into singular/simple-ish API.

It's a bit overly simple, but it's helped a few times writing code the makes use of several concurrency methods and combining them together etc.

I would love some help on this project! I have managed to get Python 3 support working in the 0.3 release for at least a few examples, and any further help with bug reporting would be very much appreciated.

There is in the latest version. Using like @concurrent(...) passes all arguments directly to Pool(...)

I am not from Facebook, but I read through your tests and found one that violates the problem description on line 74 of test/index.js. The first statement of the problem is, "If two events collide in time, they MUST have the same width." So a width of 2/3 is not possible, all widths must have a numerator of 1.

This rule is important because it makes the widths of the events deterministic, which otherwise they are not. That same test illustrates this exact problem, why not have the widths be 1/2, 1/4, 1/4, 1/2? Considering the first constraint the correct layout is all having width 1/3.

https://github.com/thejsj/calendar-exercise/blob/master/test...