Refactoring

huey.consumer.Consumer.worker_threads right now is a list of tuples (worker, process).

But the first item is never used, because it is recreated each time ( https://github.com/coleifer/huey/blob/0447c6046e7475ec31e9d0796ccc6c7f906bfaef/huey/consumer.py#L589 ). worker_threads can be a list of processes instead to make the code simpler to understand and maintain.

[mindojo-victor]

When did I say this?

I suggested the same thing here https://github.com/coleifer/huey/issues/265#issuecomment-337261204

But you suggested to use an uglier way. So I made the conclusion that you don’t want to make it easier to override the internals.

there’s an entitled vibe coming across that you may not be aware of.

Sorry, I am not a native English speaker, so I am not sure what this idiom means. But I think I understand what you mean.

I feel like I am fighting with you. To me it looks like you oppose some of changes. I kind of understand why, but I don’t think it’s wise.

That’s were my attitude comes from.

So I think I could address the same quote to you… 😃

[coleifer]

You’re correct. It makes things like testing easier to have the worker class and the associated process in the same data-structure, because once you wrap the worker class in a greenlet/thread/process, there’s no way to reference it after the fact. It’s not being used outside of the tests, at present, though. Perhaps I can make some better comments.