Brian Bouterse wrote: > I propose that we leave the 2.4 release locked in at Celery 3.1.9. I don't think that Celery bug will be on any code paths, and we can upgrade and test the latest with the 2.4.1 release. What do you think about that? Sounds fine to me. Anybody else have an opinion? -- Randy Barlow Raleigh, NC, USA