> > +1 for that, though this will need some careful design between perf
optimizations and how much general purpose it should be. Perhaps before optimising we could start out with the basic readable version and tailor it moving forward. It's possible this could be irrelevant if it's only ever used alongside heavier operations like querying a database. I remember a discussion years ago, whether this should go into python > batteries. Ended up unresolved, as the optimization goals depend alot on > the provided data structures. Maybe this can be avoided in django by > focussing on most typical nested data structures. > Interesting… that would explain its absence from itertools. It might be worth me going back through Python ML to see what was discussed. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CADyZw-69zb0GGf6ec%3D8255OMiJDs_kzs-%2Bba%3DYGsH0CPx%3D85cQ%40mail.gmail.com.
