Python Productivity over C++

[Drew Csillag]

On Fri, 9 Jun 2000, Mike  Fletcher wrote:

> Just a minor note, having spent all of last night (unsuccessfully) trying to
> track down a memory leak.  Yes, memory leak tools would be nice to have in
> Python.  Hidden memory leaks (cycles) are rare, but when they happen in a
> complex project they are often a nightmare to track down.  An optional
> garbage collector with a debug mode saying "hey, I found a cycle that wasn't
> cleaned up, the objects were: object types, object cycle description" would
> be really cool.  Yes, I'd probably remove it for the final proggy, but as a
> development tool it would be very, very, useful, and is currently (to my
> memory), not available.

Good point.  But there are actually two cycle detectors (one may or may
not be derived from the other) that I know of: plumbo and Cyclops (I've
used both).  I believe (I may be totally wrong on this) that one of them
will be included with 1.6.

> 
> 0.02
> Mike(y)
> 
> -----Original Message-----
> From: Drew Csillag [mailto:drew.csillag at starmedia.net]
> Sent: Friday, June 09, 2000 1:07 PM
> To: Steve Mullarkey
> Cc: python-list at python.org
> Subject: Re: Python Productivity over C++
> 
> 
> 
> 
> On Fri, 9 Jun 2000, Steve Mullarkey wrote:
> ...
> 
> Python's tools are very good (and don't need them a lot of the time
> anyhow).  The main thing missing is a GUI builder (but glade and PyGlade
> are getting there quickly).  Memory leak tools just don't apply (Python
> has reference counted garbage collection).  Programmers editors are
> numerous and one is included (IDLE).
> 
> ...
> 

--
print(lambda(q,p):'pmt:$%0.2f'%(q*p/(p-1)))((lambda(a,r,n),t:(a*r/
t,pow(1+r/t,n*12)))(map(input,('amt:','%rate:','years:')),1200.0))