I can understand the desire to keep the branch count low, but looking
at the number of people asking for Unicode support, and the broad
applicability it would have, and the comparitvely low demand for
row-level permissions and multi-db support, I would argue for starting
the Unicode branch now. It may be finished, tested, merged and on the
trunk before the other branches are done. I know that will make
merging the other branches more difficult, but Unicode support is in
high demand. --Ned. Adrian Holovaty wrote: On 10/13/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:Max Derkachev wrote:There were a lot of words about unicodification of Django, but things has not been moved a bit further.Or at least it would be nice to hear from someone of the core team why it can't be done (either right now or at all). I remember Jacob (I think) has said once along the lines that he's not very excited about unicodification since because of too little gain from too much effort. But the branch will be maintained by other people so why not try?Hey there,I'm very interested in getting this done, but we've got quite a few branches open at the moment. I think we should focus on merging at least one of these branches before opening another one, for the sake of everybody's sanity. Adrian -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~--- |
- Re: bump: give Gabor (or somebody else) a unicode branc... Ned Batchelder