News for hackers. Stuff that matters.
Re:Celery, non-blocking code and quest against coroutines by mdomans on Thursday June 09, 2016 @03:44PM (#11871793)
In all honesty .subtask() is more readable for me than .s()

Also, I don't want Celery to replace asyncio and/or threading.

I was trying to point out that the programming model can be back ported to Python as a way of approaching concurrency, which, without having to support "locks everywhere" is simpler to implement with GIL

Re:Celery, non-blocking code and quest against coroutines by asksol on Thursday June 09, 2016 @05:23PM (#11872495)
I think it's more readable in isolation, but when you have workflows it distracts you from what it's actually doing, making it harder to see what the purpose is at a glance. An API can probably not have many shortcuts like this, but you learn what .s does once, and then you barely notice it.

But that's my opinion and I have come to learn not everybody value succinctness in code, so you have the choice of both :o)

Had I not been constrained by backward compatibility I may have made it so that task(arg) only defines the signature of a task invocation and you'd need to do task(arg).delay() to call it remotely, and task(args)() to call it as a function locally.

Re:Celery, non-blocking code and quest against coroutines by mdomans on Thursday June 09, 2016 @05:31PM (#11872545)
Not merely a choice of mine to make - working in a team actually makes .subtask better