Python complaints

[Fredrik Lundh]

James Logajan <JamesL at Lugoj.Com> wrote:
> Sorry, but I think the price paid for "true" GC is too high for the small
> number of programs that benefit from this. Perhaps one should learn to clean
> up after oneself when cycles are expected.

Hmm.  I've recently dissected two large (and very complicated)
Python projects, and one of the major cost contributors when
going from "working code" to "production quality code" was the
time needed to hunt down a number of totally unexpected re-
source leaks.  GC would have helped in most of those cases.

(and in contrast what people claim on this list, more
syntactic sugar or static typing would have saved al-
most nothing...)

I plan to write a longer piece on this at a later time.

</F>