Antoine Pitrou added the comment: > This is especially so with Python 2.7 still having a couple of years > of full maintenance left - that's a long time to leave it with a known > broken memoryview implementation. I'm less worried about 3.2, since > the upgrade path to 3.3 is easier in that case, but even that version > is likely to see widespread use for a long time.
Well, there's a reason we don't backport features to bugfix branches, especially when we're talking about a complete rewrite of the implementation. So I really don't agree this should be backported. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12834> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
