Two manage.py/system-check warnings observed during dev-server boot:
- W340 on
program.ClassSubject.allowable_class_size_ranges — null=True has no effect on a ManyToManyField; drop it.
- W342 on
users.UserForwarder.source — unique=True on a ForeignKey; use OneToOneField instead.
Both appear pre-existing (W340/W342 predate Django 5) and are cosmetic, but easy to retire. The OneToOneField change carries a migration. Worth confirming the current field definitions and that the warnings still fire before fixing.
Two
manage.py/system-check warnings observed during dev-server boot:program.ClassSubject.allowable_class_size_ranges—null=Truehas no effect on aManyToManyField; drop it.users.UserForwarder.source—unique=Trueon aForeignKey; useOneToOneFieldinstead.Both appear pre-existing (W340/W342 predate Django 5) and are cosmetic, but easy to retire. The
OneToOneFieldchange carries a migration. Worth confirming the current field definitions and that the warnings still fire before fixing.