Antoine Pitrou added the comment: > I see no problem with that. If the internal representation changes, > nobody should be surprised if sizeof changes.
Who is "nobody"? Users aren't aware of internal representation changes. It sounds like you want sys.getsizeof() to be a tool for language implementors anyway. > I proposed a precise definition of what "an other object" is. If you don't > like it, > please propose a different definition that still allows to automatically sum > up the > memory of a graph of objects. What is the use case for "summing up the memory of a graph of objects? How do you stop walking your graph if it spans the whole graph of Python objects? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19048> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
