Mikhail T.

Patching the md5-code

The ChangeLog is stale -- not updated since 2012 -- the changes are, instead, enumerated in the ANNOUNCE. Could this be corrected, please?

Thank you for such a prompt reaction. It will take me a while to get to testing it though -- for now I'm still working with Dispy-4.10.5...

Your examples presume, the tasks are all homogeneous -- and a node either is or is not suitable for all of them. That's different from the problems I'm trying to solve, which both stem from the tasks being heterogeneous. Any node in my setup can process any task -- there is no need for any node to be excluded. But the tasks have different resource-requirements -- something a smart scheduler can help address by, for example, mixing heavy CPU-users together with heavy RAM-users. Currently, when determining,...

Feature-request: add different resource-consumption per task

Ok, then I've misunderstood the usage/purpose of the SharedJobCluster -- I only attempted to use it, when hitting the bug 19... Never mind then -- we don't even have the scheduler running. Sorry for the noise.

Ok, then I've misunderstood the usage/purpose of the SharedJobCluster -- I only attempted to use it, when hitting the bug 19... Never mind then -- we don't even have the scheduler running.

More specifically, this is our code using JobCluster. I wish, the same worked for SharedJobCluster, but it does not... def my_ip_addresses(family = socket.AF_INET): for i, nics in psutil.net_if_addrs().items(): for nic in nics: if nic.family == family: yield nic.address ... cluster = dispy.JobCluster( execTask, ... ip_addr = list(my_ip_addresses()) )