In a test environment, the current code requires SECRET_KEY to be set if PYTHONWARNINGS=error, as otherwise the code issues a warning (which PYTHONWARNINGS changes to an error, causing tests to fail).
Our CI tests use PYTHONWARNINGS=error so that any warnings from migrate, makemigrations --check, etc. cause CI to fail.
However, it's a bit annoying to have to set SECRET_KEY.
lib-cove-web should not be so concerned with core Django features. It is up to the user to deploy Django correctly.
In a test environment, the current code requires
SECRET_KEYto be set ifPYTHONWARNINGS=error, as otherwise the code issues a warning (whichPYTHONWARNINGSchanges to an error, causing tests to fail).Our CI tests use
PYTHONWARNINGS=errorso that any warnings frommigrate,makemigrations --check, etc. cause CI to fail.However, it's a bit annoying to have to set
SECRET_KEY.lib-cove-web should not be so concerned with core Django features. It is up to the user to deploy Django correctly.