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

Showing content from https://mail.python.org/pipermail/python-dev/2000-September/009113.html below:

DEBUG_SAVEALL feature for gc not in 2.0b1?

• Previous message: [Python-Dev] Re: DEBUG_SAVEALL feature for gc not in 2.0b1?
• Next message: [Python-Dev] Re: DEBUG_SAVEALL feature for gc not in 2.0b1?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Neil Schemenauer wrote:
> 
> On Fri, Sep 01, 2000 at 11:08:14PM +0200, Vladimir Marangozov wrote:
> > Also, I support the idea of exporting the collected garbage for
> > debugging -- haven't looked at the patch though. Is it possible
> > to collect it subsequently?
> 
> No.  Once objects are in gc.garbage they are back under the users
> control.  How do you see things working otherwise?

By putting them in gc.collected_garbage. The next collect() should be
able to empty this list if the DEBUG_SAVEALL flag is not set. Do you
see any problems with this?

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

• Previous message: [Python-Dev] Re: DEBUG_SAVEALL feature for gc not in 2.0b1?
• Next message: [Python-Dev] Re: DEBUG_SAVEALL feature for gc not in 2.0b1?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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