Upgrade to django 3.2
As a first step, we need to determine how much work will be involved with this change and what impact it will have on pulpcore and plugins.
#2 Updated by daviddavis 8 days ago
Here's my branch: https://github.com/daviddavis/pulpcore/tree/django3
Most of everything is working aside from the task code (more on this below). The django-guid package has a 3.x version which they recommend using since it supports ASGI. However, it does not support Python 3.6. But it appears that django-guid 2.2 is working for now.
The biggest change will be handling django's ORM in our async code. Django's ORM is not async safe and therefore you have to use
sync_to_async() when calling django's ORM (otherwise you get an error).
Alternatively, there is a variable we can set
DJANGO_ALLOW_ASYNC_UNSAFE but I don't think we should go this route. From the django docs, it says, "do not use this in production environments".
 "SynchronousOnlyOperation: You cannot call this from an async context - use a thread or sync_to_async"
Please register to edit this issue