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 issu
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:5
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/int
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 di
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
On Wednesday, June 28, 2017 at 7:10:35 AM UTC-4, Drunkard Zhang wrote:
>
> Hi, fellows:
>
> I was runn
Hi, fellows:
I was running python-3.4+django-1.9.13 previous, and upgrading to
python-3.6+django-1.11.2, while testing, I found that my limit_choices_to
function not working now, here's detail.
I'm using a middleware to get current user who is accessing my site, and
use it in limit_choices_to
6 matches
Mail list logo
