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/006155.html below:

[Python-Dev] Memory leak tracking

[Python-Dev] Memory leak trackingGreg Stein gstein@lyra.org
Tue, 11 Jul 2000 17:50:56 -0700
On Wed, Jul 12, 2000 at 02:11:06AM +0200, Vladimir Marangozov wrote:
> 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.

Agreed. The core should never create refcount problems. With or without GC,
that is just bad policy.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/



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