Hi Erik,
On 5/13/19 8:22 PM, Erik Stein wrote:
Hello everyone --
From time to time I come accross a potential bug in Django core, but
because of a tight schedule don't have the time to dive into it and
write a proper ticket. How would you suggest to deal with it?
my personal position would be to open a ticket with what information you
_do_ have, so the discovery is not lost.
The "worst case" is one of the ever efficient Django Fellows comes by,
tests it out, and closes it as "works as expected".
If you _don't_ log the issue, it _will_ be forgotten about, because
we're all human. :)
Today e.g.
– Using i18n_patterns with prefix_default_language=True,
– trying to get the frontpage URL without a language given in the URL
works in debug mode, but gives an internal server error without any
backtrace in production mode.
This was caused by a buggy 404.html template, but probably buggy 404
templates should give a backtrace, too, and i18n_patterns shouldn't be
concerned by this anyway.
Certainly a solution worthy of discussion!
Are those notes something which should get into Trac to be investigated
later?
Absolutely yes!
Thanks for you opinion and guidance,
--
Curtis
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" 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-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/f91ecd30-a077-956c-a5af-1027359c65f2%40tinbrain.net.
For more options, visit https://groups.google.com/d/optout.
