> On Dec 17, 2014, at 5:48 PM, Carl Meyer <c...@oddbird.net> wrote: > > On 12/17/2014 04:39 PM, Russell Keith-Magee wrote: >> >> I agree that lists are preferable to tuples. >> >> One option for handling existing projects might be to define our own >> subclass of list that defines __add__, __iadd__, and __radd__ such that it >> will accept a tuple, converting to a list, and raise a DeprecationWarning; >> in a later version, we can replace that subclass with a simple list. We >> wouldn't document this class, and it would only be used in >> global_settings.py. This would cover the most common use case (adding >> something to a default setting), and provide a migration path. Thoughts? > > FWIW, I think the subclass-of-list approach is neat enough, I'd be in > favor of going ahead and doing this with that approach, if someone's > motivated to write the patch. > What would __iadd__ do in this subclass? Would it behave like tuple and create a new DjangoList, or would it behave like list and extend the original list?
I’m interested at taking a whack at it, though I can imagine somebody else getting it done faster. Ryan -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/D0921E76-49EC-4750-8013-DE117AEC5544%40ryanhiebert.com. For more options, visit https://groups.google.com/d/optout.
