Fixtures Result in Runtime Warnings while time zone support is active

[michaelhiiva]

Summary of Bug

On new the creation of new local app container the following error results: RuntimeWarning: DateTimeField Member.last_changed received a naive datetime (2020-07-18 00:00:00) while time zone support is active. Application still runs; however, there may be future issues if there is a need for timezone support.

Steps to Reproduce the Behaviour

1) docker-compose up

The Expected Behaviour

The scripts/make_fake_fixtures.py creates Django valid dates with timezone support which can be added to the database for local development.

References

• Time zones | Django Fixtures
• https://github.com/usgo/agagd/pull/125#pullrequestreview-505093287
• https://github.com/usgo/agagd/pull/125#issuecomment-706756328

  Also there are a lot of:

  RuntimeWarning: DateTimeField Member.last_changed received a naive datetime (2020-07-18 00:00:00) while time zone support is active.

  which might be worth dealing with.