Guido van Rossum <guido@digicool.com> writes:
> > Cute! Hard to explain, unless someone is using PyDict_Next on this dict:
> > since the dict has 11 items, it's exactly at the boundary where PyDict_Next
> > will now resize it.
>
> It *could* be the garbage collector.
I think it would have to be; there just aren't that many calls to
PyDict_Next around. I confused myself by thinking that calling keys()
called PyDict_Next, but it doesn't.
glad-that-one's-sorted-out-ly y'rs
M.
--
"The future" has arrived but they forgot to update the docs.
-- R. David Murray, 9 May 2000
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4