Also, found the patch I wrote: https://gist.github.com/jarshwah/a541857db195f0486b9e
Instead of multiple subclasses, perhaps Func could take on some of the functionality of transform directly, but that makes no sense for > 1 arity functions. A nice design should be able to be found. On Thursday, 26 March 2015 05:28:51 UTC+11, Anssi Kääriäinen wrote: > > Transforms are just single argument expressions available using lookup > strings. The biggest complication is that Transforms have slightly > different API to expressions. > > I don't see a reason why transforms couldn't be a special case of > expression. There are some API incompabilities, but they should be solvable. -- 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/efda77ae-033d-41d4-a878-fa32ab3dd2c7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
