Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Michael Fladischer <michael@fladi.at>
Newsgroups: linux.debian.maint.python
Subject: Re: django-celery
Date: Fri, 27 Apr 2018 09:20:01 +0200
Message-ID: <vJ5PH-2Ar-11@gated-at.bofh.it>
References: <vJ53j-1OA-1@gated-at.bofh.it>
Old-Return-Path: <michael@fladi.at>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Approved: robomod@news.nic.it
Lines: 19
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:10478

Hi Brian,

On 27/04/2018 08.22, Brian May wrote:
> Beginning to think we should seriously think about dropping this
> package. It is badly neglected by upstream, and there are now better
> alternatives. Such as django-celery-results (not sure if this is in
> Debian).

I'm completely with you on this. As the one who initially packaged 
django-celery it's time to drop it. Both its successors, 
django-celery-results and django-celery-beat are packaged for Python3 
(Python2 support can always be added if someone wants to step in) in Debian.

The only thing left to do is to find a way to do the transition to those 
new packages. I'm thinking about mentioning this in NEWS.Debian for 
django-celery as any automatic transition does not seem feasible.

Regards,
Michael