Django 3.2 branch is deployed to registry-stg and registry-prd, but Calisphere also uses exhibitapp and is still on Django 1.11
We should either upgrade Calisphere to use Django 3.2 very soon, or tag master prior to merging this PR and continue to use the outdated tagged version in Calisphere. Let's hold on merging this PR until we've made that decision.
Changes required for an upgrade to Django 3.2
Django 3.2 branch is deployed to registry-stg and registry-prd, but Calisphere also uses exhibitapp and is still on Django 1.11
We should either upgrade Calisphere to use Django 3.2 very soon, or tag master prior to merging this PR and continue to use the outdated tagged version in Calisphere. Let's hold on merging this PR until we've made that decision.