#9104: FieldDoesNotExist is defined in "confusing" place. -------------------------------------+------------------------------------- Reporter: telenieko | Owner: nobody Type: | Status: new Cleanup/optimization | Component: Core (Other) | Version: master Severity: Normal | Resolution: Keywords: | Triage Stage: Design | decision needed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by claudep): Of course, my "trick" about a `FieldDoesNotExist.py` file only works if we want to loudly fail with an explicit message. Still looking for a way to raise a warning without ever calling the symbol (might be impossible...). -- Ticket URL: <https://code.djangoproject.com/ticket/9104#comment:11> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.bc429f935d26c0b0ba59facc2e445b48%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.