Raymond Hettinger <raymond.hettin...@gmail.com> added the comment:
Markus, thank you for the suggestion but I'm going to decline. When this rough equivalent was first created, we looked at several recipes and chose this one as being one of the least magical. Intentionally, we did not use the variant you've proposed. To a person well versed in recursion and in generator chains it makes sense but not so much for anyone else. Plus it is hard to step through by hand to see what it is doing. In general, the rough equivalents were intended to a way to understand what output is going to be generated. That is why they are mostly simple rather than being faithful to the actual implementations (otherwise, we would use classes rather than generators for all the equivalents). Viewed in this light, we place almost zero weight to making the recipe memory efficient with respect to temporary variables. ---------- resolution: -> rejected stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46379> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
