Kristján Valur Jónsson <krist...@ccpgames.com> added the comment: >The malloc >implementation just has no business looking at the thread state.
Of course it does, if it you want to have any hope of instrumenting your python memory usage with detailed python runtime information. Your statement islike saying: "A profiler has no business looking at the thread callstack." Note that we are not making any new requirements on python here. Merely facilitating the process, for those implementations that _wish_ to do so (at their own risk.) So, although you have nothing against the patch as such, you are against it on the principle that I am using it to facilitate something that you disapprove of. I find that a quite unreasonable position. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9787> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
