Hi, I wanted to raise this ticket for discussion as to what the best solution might be. As suggested in the ticket, I think adding a setting to control the number of cache attempts instead of hard-coding "10000" might be a reasonable approach. I'm not sure if that solution would be considered a "feature addition" (adding a new setting) and thus not appropriate for this stage of the release cycle.
Has anyone else experienced the issue and devised a workaround? It's a minor issue since the side-effect seems to be that the login silently fails and a user must retry. Thanks, Tim -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
