Xiang Zhang added the comment: I'm -1 if the intention is about easiness and efficiency.
I think a new API is usually added due to functional defect not performance defect. We get a way here though the performance seems not ideal, according to INADA's mail. I think we should first check if memoryview gets an optimization chance to fit more in such a case. Creating a memoryview is not cheap enough in such a case. About easiness to use, when a user considering such low level details, it's reasonable to know memoryview and it needs to be released. But if this API is added to simplify bytes(), I think it makes sense but it's not only about adding a frombuffer(). ---------- nosy: +xiang.zhang _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29178> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
