This uses the standard name as specified in the cfgov-django-setup repo for the setup.py config.
This does not need to be deployed and can wait for the next substantive change for a release.
The current config will work thanks to permissive pypi name-handling, but we should use the proper name for our own package.
Coverage remained the same at 100.0% when pulling f8c698b62bda14929a638c9a9dc95d1ea25bbc95 on fix-import-name into a75769f0df9d1ceabaf991cf83e4dba8b48c308b on master.
This uses the standard name as specified in the cfgov-django-setup repo for the setup.py config.
This does not need to be deployed and can wait for the next substantive change for a release. The current config will work thanks to permissive pypi name-handling, but we should use the proper name for our own package.