Django-dramatiq

Changed
- Replaced `AppConfig.ready` workaround with `__init__` to fix [133]. ([amureki], [137])

[amureki]: https://github.com/amureki
[133]: https://github.com/Bogdanp/django_dramatiq/issues/133
[137]: https://github.com/Bogdanp/django_dramatiq/pull/137

Added
- Support for Python 3.10 and 3.11
- Support for Django 4.0 and 4.1

Changed
- Fixed issue [123] in deferred `DjangoDramatiqConfig` initialization.
Dramatiq configuration now happens before loading importing all Django apps models,
so loaded tasks will use the correct Dramatiq settings. ([amureki], [126])

Dropped
- Support for Python 3.6
- Support for Django 2.2 and 3.1

[amureki]: https://github.com/amureki
[123]: https://github.com/Bogdanp/django_dramatiq/issues/123
[126]: https://github.com/Bogdanp/django_dramatiq/pull/126

Added

- The `DRAMATIQ_AUTODISCOVER_MODULES` setting. ([thebjorn], [97], [98], [99])
- The `--worker-shutdown-timeout` flag to `rundramatiq`. ([b1ngz], [110])

Changed

- Initialization is now deferred until the application is ready. This
is somewhat of a major change to how configuration works, but it's
more in line with what Django expects from apps. If you run into
issues importing your tasks, consider deferring your imports as much
as you can (eg. import tasks in your methods instead of at the top
level). ([103])

[b1ngz]: https://github.com/b1ngz
[thebjorn]: https://github.com/thebjorn
[97]: https://github.com/Bogdanp/django_dramatiq/issues/97
[98]: https://github.com/Bogdanp/django_dramatiq/issues/98
[99]: https://github.com/Bogdanp/django_dramatiq/issues/99
[103]: https://github.com/Bogdanp/django_dramatiq/pull/103
[110]: https://github.com/Bogdanp/django_dramatiq/pull/110