Antoine Pitrou added the comment: > Can we agree on discarding the current implementation for now and then > rewriting it based on a tree builder instead of a parser wrapper?
Only if it actually brings something (feature-wise, performance-wise, maintenance-wise, whatever) that the current implementation doesn't have. Otherwise, I'd rather check in the simple inheritance-to-composition change. I'm sorry that you noticed this after the alpha. I would have had a lower threshold for changes if you had manifested when I proposed the feature. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17741> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
