❦ 24 décembre 2017 22:25 +0200, Timo Aaltonen <tjaal...@debian.org> :
> On PyPy, though, it always raises TypeError. Before looking for
> alternatives, please take a moment to read the following explanation as
> to why it is the case. What you are looking for may not be possible.
>
> A memory profiler using this function is most likely to give results
> inconsistent with reality on PyPy. It would be possible to have
> sys.getsizeof() return a number (with enough work), but that may or
> may not represent how much memory the object uses. It doesn't even
> make really sense to ask how much *one* object uses, in isolation
> with the rest of the system. For example, instances have maps,
> which are often shared across many instances; in this case the maps
> would probably be ignored by an implementation of sys.getsizeof(),
> but their overhead is important in some cases if they are many
> instances with unique maps. Conversely, equal strings may share
> their internal string data even if they are different objects---or
> empty containers may share parts of their internals as long as they
> are empty. Even stranger, some lists create objects as you read
> them; if you try to estimate the size in memory of range(10**6) as
> the sum of all items' size, that operation will by itself create one
> million integer objects that never existed in the first place.
>
> --------------------------------------------------------------------
>
> How to proceed from here?
Upstream of pyasn1 is responsive. I can copy-paste your text in a pull
request making "TypeError" an acceptable result. In the meantime, the
test can be patched on Debian.
Do you expect one of us to upload or did you want to do that yourself
(both are fine for me)?
--
Anyone who has had a bull by the tail knows five or six more things
than someone who hasn't.
-- Mark Twain
signature.asc
Description: PGP signature
