Le jeudi 1 novembre 2012 14:32:12 UTC+1, Russell Keith-Magee a écrit : > > > However, this all hinges on someone getting: > > 1) consensus on a design, > 2) a commit-ready patch that implements that design. > > Reading the ticket, we haven't yet achieved (1). The most recent comment > was 9 months ago, and hasn't been followed up. For the record, that comment > doesn't "promise" anything -- it's just saying that if a change is going to > happen, it couldn't happen any sooner than 1.5 (since 1.4 was already out, > and a change like this *won't* be back ported). > > So - if you want this, now would be a very good time to do exactly what > the ticket says, and lead the discussion advocating it. >
For me, changing the outcome of validate_slug is not an option, like Paul wrote on the ticket. I'd suggest: a) creating a new validate_uslug validator (better name anyone?) b) allowing a custom validator to be passed to the SlugField constructor Claude -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/bSf-Oj3VOH0J. 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.
