any objection to making task take a float as opposed to an int?

[sanga]

This would make it a lot easier to make one task very unlikely when you have many tasks (i.e. currently you need to make all the others much more likely, with the proposed change you'd just need top make that one task say "task(0.001)")

I haven't looked at this at all but I suppose this would be a not too difficult change (which I might make a PR for should you agree that it's desired and should you not beat me to it)

[sanga]

I had a go at doing this last night and seems to work just fine. By making the tasks attribute a list of the format [(func, weight)] and then doing a weighted random choice from that list rather than having the func be present in the list multiple times to make it more likely to be selected. Sound reasonable? (I'll push a branch when I have a moment to detangle that change from some other work).

[Jahaja]

Sounds like an improvement indeed. A pull request would be much appreciated :)