- Package:
- src:django-celery-email
- Source:
- src:django-celery-email
- Submitter:
- Colin Watson
- Date:
- 2024-08-04 16:39:03 UTC
- Severity:
- normal
django-celery-email seems to have been unmaintained upstream for some time; the last release was in 2019, and the last upstream commit was in 2022. I was looking around and saw that https://pypi.org/project/django-celery-email-reboot/ seems to be a somewhat more active fork. I'm not sure what would make most sense here. Is it worth considering switching this package's upstream to django-celery-email-reboot? Or should django-celery-email-reboot perhaps be packaged separately instead? Thanks,