#30475: Use of i18n_patterns and a buggy 404 template trigger internal server
error
without a backtrace
-----------------------------+--------------------------------------
Reporter: Erik Stein | Owner: nobody
Type: Bug | Status: closed
Component: Core (URLs) | Version: 2.2
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => needsinfo
Comment:
Replying to [ticket:30475 Erik Stein]:
> [draft bug report, I'll try to provide more details later or on request]
Hi Erik.
Happy to look at this but, as Claude says, could you provide a sample
project the reproduces the issue?
What **exactly** is the issue? An error in the 404 template? That i18n
patterns swallows that? (Is it in fact dependent on i18n patterns?) And so
on.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/30475#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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.8637f5a45754c45081f4367dca2839f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.