Antoine Pitrou <pit...@free.fr> added the comment: > > The expectation is that it returns the memory footprint of the given > > object, and only it (not taking into account sharing, caching, > > dependencies or anything else). > > It would be nice if this was a well-defined definition, but > unfortunately it is not.
I didn't claim it was. Actually, if you read the rest of my message, I did mention that PyPy could tweak the semantics if it made more sense. So, of course, the more sharing and caching takes place, the less obvious these semantics are, but even with CPython they are not obvious anyway. It's not supposed to be an exact measurement for the common developer, rather a hint that experts can use to tweak their data structures and algorithms; you need to know details of your VM's implementation to use that information. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10994> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
