the edgewall trac release 0.11 is blocked now since more than one
month for a memory leak nobody is able to find, see
http://groups.google.com/group/trac-dev/browse_thread/thread/116e519da54f16b
.
does python-3.0 improve something to avoid writing memory leaking
applications?
rupert.
--
Hi Rupert,
-On [20080210 20:16], rupert.thurner ([EMAIL PROTECTED]) wrote:
the edgewall trac release 0.11 is blocked now since more than one
month for a memory leak nobody is able to find, see
http://groups.google.com/group/trac-dev/browse_thread/thread/116e519da54f16b
.
You are slightly
Jeroen Ruigrok van der Werven wrote:
For me, a relative newbie to Python, the entire memory allocation issue is
not transparent at all and information about it is scattered across the net.
One of the things I hope to contribute to in the coming year is to make sure
the entire area of Python
rupert.thurner wrote:
does python-3.0 improve something to avoid writing memory leaking
applications?
No, it doesn't. Python 3.0 and maybe 2.6 are going to have some small
improvements but the improvements aren't related to memory leaking. I'm
working on the matter for a while now. I've limited
On Feb 10, 9:08 pm, Christian Heimes [EMAIL PROTECTED] wrote:
rupert.thurner wrote:
does python-3.0 improve something to avoid writing memory leaking
applications?
No, it doesn't. Python 3.0 and maybe 2.6 are going to have some small
improvements but the improvements aren't related to
