Re: django-celery
On 04/27/2018 08:22 AM, Brian May wrote: > Hello, > > 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 attempted to fix it by upgrading to the latest upstream version (see > git repository), but there are a number of python errors running tests, > and I lack the interest in attempting to fix them (although at quick > glance some of these errors look trivial to fix...) > > As far as I am aware, nothing in Debian depends on django-celery. > > Any thoughts? I agree as well. Please file a bug for its removal. Cheers, Thomas Goirand (zigo)
Request joining DPMT
Hi, I currently maintain the mpd-sima and python-musicpd packages. I would like to maintain python-musicpd within the DPMT, which is why I am hereby requesting to join the Debian Python Modules Team. My Salsa login is kaliko-guest (same as my Alioth login). I have read the DPMT Policy [0], and I accept it. Thank you! Cheers k [0] https://python-modules.alioth.debian.org/policy.html signature.asc Description: OpenPGP digital signature
Re: django-celery
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
