Closed loicteixeira closed 3 years ago
The Django 3.0 warning comes from Django-Bakery and it doesn't seem to be a fix there. However, it's a deprecation warning for Django 4.0, so there is no rush.
The Python 3.9 warning comes form Wagtail itself. I submitted a PR, see wagtail/wagtail#6241.
Working through the ones thrown by Wagtail-Bakery itself on #54.
Wagtail 2.9 warning (for Wagtail 2.11 compatibility) have been taken care of in #58
Using Wagtail Bakery with Django 3.0, Wagtail 2.8 or Wagtail 2.9 produces some Deprecation Warnings. Some seem to be upstream so we might not be able to do much, but listing them here anyway.