My apologies. I have solved this problem myself. I separated my models to their own files because they got over 2K lines, and I named the file the attachment model lives in Attachment.py. Because the module-level function getUploadPath and Attachment's getUploadPath both have the same name, Django's migration autodetector tries to access "backend.models.Attachment.getUploadPath" but the Attachment module is overwritten by the Attachment class in backend/models/__init__.py: "from .Attachment import Attachment". I ended up renaming all the model files to remove the ambiguity and then recreating my migrations. Apologies for wasting your time! ^^
Best Regards,
m712 - Developer
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/58f092bf.88c61c0a.ca951.fe8eSMTPIN_ADDED_MISSING%40gmr-mx.google.com.
For more options, visit https://groups.google.com/d/optout.
