Michael Bridgen

> Just to be clear, does done() exit the program? I ask because exiting, or closing the context, will drop any frames in sockets on the ground. The way to...

I'm not quite sure what you're asking for -- can you sketch out how it would look? (In code, or pseudo-code, perhaps)

Ah, I see! OK, that is a worthy aim. Let me take a look at it ..

Part of the contract of push or req is that the message goes to a single consumer. Routing (i.e., sending to an exchange rather than a queue) breaks the contract...

I think I see: you have a bunch of different kinds of job, and you want to be able to partition them into a smaller number of queues, for workers...

> there are hundreds of jobs and dozens of job types that will be built, changed, maintained and updated over the years. It's not something that can be set up...

> So with all that in mind, what do you think of the TASK socket? I think this would survive dozens of job types (after all, every sub socket has...

I've implemented the TASK socket in master. (If it turns out I'm off track, we can think of it as an hilarious April Fools prank.)

@derickbailey I'm interested to hear where this ended up for you -- did you get something working in a fork, try the TASK socket, do something completely different ..?

I don't think it was that change. I can run the tests to completion on HEAD: ``` $ pytest --hypothesis-show-statistics -v =============================================================================================== test session starts =============================================================================================== platform linux2 -- Python...