This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients LambertDW, benjamin.peterson, darrenr, loewis
Date 2009-01-02.16:01:38
SpamBayes Score 2.95657e-08
Marked as misclassified No
Message-id <1230912099.82.0.660538055717.issue4794@psf.upfronthosting.co.za>
In-reply-to
Content
Hard real-time applications written in Python should not rely on the
cyclic garbage collector. They should call gc.disable at startup, and
completely rely on reference counting for releasing memory. Doing so
might require rewrites to the application, explicitly breaking cycles so
that reference counting can release them.

Even with cyclic gc disabled, applications worried about meeting hard
deadlines need to look even more into memory allocation and
deallocation; e.g. releasing a single object may cause a chained release
of many objects, which can affect worst case execution times. There are
more issues to consider (which are all out of scope of the bug tracker).
History
Date User Action Args
2009-01-02 16:01:40loewissetrecipients: + loewis, benjamin.peterson, LambertDW, darrenr
2009-01-02 16:01:39loewissetmessageid: <1230912099.82.0.660538055717.issue4794@psf.upfronthosting.co.za>
2009-01-02 16:01:39loewislinkissue4794 messages
2009-01-02 16:01:38loewiscreate