#26896: FileSystemStorage no longer accepts reverse_lazy as base_url -------------------------------------+------------------------------------- Reporter: tpazderka | Owner: nobody Type: Bug | Status: new Component: File | Version: 1.8 uploads/storage | Severity: Normal | Resolution: Keywords: storage, | Triage Stage: reverse_lazy | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by tpazderka): Not exactly our usecase as our failure is on `ImportError` which seems hard to test, but I hope that this patch shows the issue we are having. The basic idea is that `reverse_lazy` should remain lazy as long as possible. Resolving the `base_url` on `init()` defeats the purpose of using `reverse_lazy` there. -- Ticket URL: <https://code.djangoproject.com/ticket/26896#comment:2> 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.73e5fadd91a1f5a01168b0012d3bf114%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.