The new ticket is https://code.djangoproject.com/ticket/28345.

On Wednesday, June 28, 2017 at 5:03:54 PM UTC-4, Tim Graham wrote:
>
> A new ticket is appropriate since the changes for the original ticket are 
> already released. Please include more explicit steps about how to reproduce 
> the issue -- it's difficult for me to tell exactly what the issue is from 
> the details you provided so far.
>
> On Wednesday, June 28, 2017 at 10:42:50 AM UTC-4, Drunkard Zhang wrote:
>>
>>
>>
>> On Wednesday, June 28, 2017 at 10:11:35 PM UTC+8, Drunkard Zhang wrote:
>>>
>>>
>>>
>>> On Wednesday, June 28, 2017 at 7:56:36 PM UTC+8, Tim Graham wrote:
>>>>
>>>> To get some insight, I'd try bisecting to find the Django commit where 
>>>> the behavior changed:
>>>>
>>>> https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/#bisecting-a-regression
>>>>
>>>>
>>> After a whole day digging that, I found the commit changed the 
>>> behaviour: 6abd6c598ea23e0a962c87b0075aa2f79f9ead36, and the ticket: 
>>> https://code.djangoproject.com/ticket/27563
>>>
>>> I'm feeding back to upstream.
>>>
>>>>
>>>> Should I open a new regression report for this? 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" 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-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/58e67f67-f060-44b1-892f-f80e3ad88376%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to