Dave Chevell

In that case, I might just publish my fork under a different name. To your point about handling movies like life Runner 2049, my proposed changes here would handle that...

There's no real reason to only support 2020 dates. Come 2030 this will just break again - if we're going to fix it, why not just support dates up to...

@manolosolalinde what would that behaviour look like? For the most part we're just wrapping the `concurrent.futures` API: https://docs.python.org/3/library/concurrent.futures.html You can already set timeouts on _retrieving_ results from a `future` in...

I'm closing this out for now, most use cases would be solved by the existing timeout functionality (even using it at the point of retrieving results would effectively time them...

I believe @aaronyo was right - and wouldn't be surprised if the "other objects" aren't actually sharing state between processes any more than this library. Solving via `redis` has nothing...

This is a good catch and a bit of a fail on my end: * The callback effectively _logs_ the exception, so it seems to appear * If the callable...

I believe some of the underlying lib changes in the intervening years should solve for everything here, tasks are run under a new application context which have a copy of...

Closing this out, the answer is indeed yes, but worth remembering that since gunicorn forks multiple processes any attempt to use things like `submit_stored` will yield unexpected results, as this...

Wouldn't call that ugly, I'd call that the standard expectation for every Flask extension. Could add some kind of workaround parameter but there are enough "how do I run Flask-related...

I'll close this for now, but @davidferguson may be interested in #35