Please see https://code.djangoproject.com/ticket/25731 for some discussion. Feel free to offer a patch so we can assess if it's feasible.
On Sunday, January 24, 2016 at 2:57:04 PM UTC-5, is_null wrote: > > Hi all, > > In Select widgets, as well as many other (including MultipleHiddenInput, > where it's not used) rendering methods all have a choices=() kwarg and use > a chain(self.choices, choices) when rendering. > > Maybe I'm missing something, but it seems like this has just been sitting > there since 2006 and all the sensible use cases for this have disappeared: > why would anyone do the effort of adding a widget-specific override in > Form.as_widget to add choices to rendering that won't even validate ? > > Can we engage deprecation on the choices argument in render methods and > rely on self.choices only or am I missing something ? > > If so, do you know if any work on this has been started ? > > Best > > James > -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/480c6bde-7e4a-4b91-b7cd-43bdb9ea46fb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
