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/2000-July/006147.html below:

[Python-Dev] Memory leak tracking

[Python-Dev] Memory leak tracking [Python-Dev] Memory leak trackingVladimir Marangozov Vladimir.Marangozov@inrialpes.fr
Wed, 12 Jul 2000 02:11:06 +0200 (CEST)
Barry A. Warsaw wrote:
> 
> How important is it to fix these problems when gc is disabled?
> ...
> Please let me know what you think.  If the concensus is to fix them, I
> keep working on them.  I do still plan on looking at the few memory
> problems still left even with gc turned on.

I think that if we start relaxing our attention w.r.t. refcount policies,
cyclic refs and the resulting mem leaks _in_the_core_, just because gc
helps in hiding bad practice, we'll suffer more than you would in the
attempt to fix these things.

-- 
       Vladimir MARANGOZOV          | Vladimir.Marangozov@inrialpes.fr
http://sirac.inrialpes.fr/~marangoz | tel:(+33-4)76615277 fax:76615252



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