Re: Unicode SlugField

59 views
Skip to first unread message

Florian Apolloner

unread,
Nov 1, 2012, 8:27:18 AM11/1/12
to django-d...@googlegroups.com
Hi,

it surely won't change in 1.5 since we already released an alpha.

Cheers,
Florian

Russell Keith-Magee

unread,
Nov 1, 2012, 9:31:45 AM11/1/12
to django-d...@googlegroups.com
On Thu, Nov 1, 2012 at 8:27 PM, Florian Apolloner <f.apo...@gmail.com> wrote:
Hi,

it surely won't change in 1.5 since we already released an alpha.

That's incorrect -- it's still possible. Alpha is the freeze for "big" features. Little features can still be added up till the release of the beta. A minor enhancement to an existing field would definitely fall under the category of a minor feature.

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.

Yours,
Russ Magee %-)

Claude Paroz

unread,
Nov 1, 2012, 9:39:17 AM11/1/12
to django-d...@googlegroups.com
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
Reply all
Reply to author
Forward
0 new messages