How to deal with potential Django bugs you come accross

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

How to deal with potential Django bugs you come accross

Erik Stein-2

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?

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.

Are those notes something which should get into Trac to be investigated
later?

Thanks for you opinion and guidance,

-- erik


--
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 [hidden email].
To post to this group, send email to [hidden email].
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/6e03157c-770a-cfe6-1569-e0f0c2aee122%40classlibrary.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: How to deal with potential Django bugs you come accross

Curtis Maloney-2
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 [hidden email].
To post to this group, send email to [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

Re: How to deal with potential Django bugs you come accross

Erik Stein-2

Hey Curtis --

thanks for your answer! I'll do this from now on (and of course I'll try
me best to write a complete bug report including a proposed fix if the
time allows).

https://code.djangoproject.com/ticket/30475#ticket

Have a nice day

-- erik


On 13.05.19 18:19, Curtis Maloney wrote:

> 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 [hidden email].
To post to this group, send email to [hidden email].
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/2c2b42de-e97c-aca6-0acf-21ed84c20c33%40classlibrary.net.
For more options, visit https://groups.google.com/d/optout.