A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-December/106470.html below:

[Python-Dev] gc ideas -- sparse memory

[Python-Dev] gc ideas -- sparse memory [Python-Dev] gc ideas -- sparse memoryGreg Ewing greg.ewing at canterbury.ac.nz
Sun Dec 5 23:29:27 CET 2010
Martin v. Löwis wrote:
> The hole C API would break if objects would move in memory.
> Since they have to stay at fixed addresses, it's easy enough to use the
> address as ID.

Yes. Some of the discussion here seems to be assuming that the
reason Python doesn't move objects is so that it can use the
address as a unique ID. But it's the other way around.

-- 
Greg

More information about the Python-Dev mailing list

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