I find celery quite convenient for background, scheduled and distributed task processing, the problem I have is that celery with turbogears is not as simple as celery on django, and while tgext.asyncjob is enough for most common use cases it would be good to have an option, I saw that there is a celery-pylons but looks like a minimal integration, thus I began working on tgext.celery which I expect to release soon with the aim of being as convenient and easy to get up and running as django-celery.
Regards, Carlos Daniel Ruvalcaba Valenzuela On Tue, Nov 27, 2012 at 8:26 AM, kgk <[email protected]> wrote: > >> >> >> You might want to give a try to a tasks queue like celery and see if you >> have better results. >> I'm also open to any patch to asyncjob, feel free to send them if you end >> up implementing changes. > > > Actually I was comparing to celery. I realized that could many of things > with multiprocessing that I needed with celery. Basically it would be nice > to start with threading or local processes and then move to remote processes > if the need arises in production. Celery looks like a good solution, but > takes more initial setup time and I not sure if its full capabilities are > needed. > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/turbogears/-/iV6vsCcPfQ0J. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/turbogears?hl=en. -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
