Thank you everybody, requests it is then! 👌 On Wednesday, May 2, 2018 at 2:40:29 AM UTC+10, Jonathan Vanasco wrote: > > If your synchronous tasks are done "quickly" or must be "blocking" -- like > doing some oAuth or hitting an external API that is guaranteed to return a > request within a second or two, I would just use `requests` from within > Pyramid. >
Yup, quick API calls that can be blocking. On Wednesday, May 2, 2018 at 2:40:29 AM UTC+10, Jonathan Vanasco wrote: > If you're concerned with extended processing on your end, or not using > systems that guarantee a response within a given amount of time... I would > use Pyramid to trigger a Celery task, and then have the page reload every 5 > seconds to poll the Celery backend for status. > Jonathan, funny you mention Celery. I have used it for a while but the experience has been horrible—the thing is ridden with bugs and problems, barely maintained, and the list of issues on Github grows daily. Which is why I raised this discussion: https://stackoverflow.com/questions/46517613/python-task-queue-alternatives-and-frameworks Curious though, I rolled the Celery task integration myself because I didn’t find any specific module for Pyramid. Is there some explicit support module out there? Cheers, Jens -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/f07117af-3200-44ed-a89b-cbfc724dcf77%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
