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/2001-March/013428.html below:

[Python-Dev] Patch for Weak References for Functions

[Python-Dev] Patch for Weak References for Functions [Python-Dev] Patch for Weak References for FunctionsPaul Prescod paulp@ActiveState.com
Fri, 09 Mar 2001 18:19:41 -0800
Phil Thompson wrote:
> 
>...
> 
> To be honest, I don't see why weak references have been implemented as a
> bolt-on module that only supports one particular object type. The thing
> I most like about the Python implementation is how consistent it is.
> Weak references should be implemented for every object type - even for
> None - you never know when it might come in useful.

Weak references add a pointer to each object. This could add up for
(e.g.) integers. The idea is that you only pay the cost of weak
references for objects that you would actually create weak references
to.

-- 
Python:
    Programming the way
    Guido
    indented it.



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