oldStatesman said:
Thanks!
If you contact him, please tell him that his writing style is very accessable..a non-programmer such as myself (I am system engineer/sdmin type) was able to comprehend it easily. I found it very helpful - now I really know what Harkonnen and you and others are talking about when they discuss mallocs and allocs and such...big thumbs up!
OK, closing the loop on my email with Evan Jones.
Nothing helpful here, but he echos what Harkonnen is saying.
Following is the email exchange:
On Nov 11, 2005, at 19:51, Paul Batte wrote:
> Do you know if this issue was ever addressed in later releases of
> Python?
My patch has not yet been committed to any branch of Python. However,
there has been interest in committing it, but I just don't have the
time or energy to try and "push" the patch through the Python developer
community. Since it touches a VERY critical section of the Python
interpreter (memory allocation) it needs very careful review and
testing.
Additionally, it probably no longer applies cleanly against the
development branch.
> The reason I am asking is like you I am a computer games addict,
> though really addicted to one game, Civilization.
> Civ IV came out about 2 weeks ago, and the bulk of the game was
> written in Python.
> The game appears to have some severe memory problems.
Hmmm! Interesting. The chances are that my patch would not solve the
problem. My patch only solves the problem IF the Python program
allocates a LOT of objects and then frees them, and never uses them
again. I would think that Civ 4 is creating a lot of objects and
keeping them around, or is creating and freeing a lot of objects fairly
quickly.
> BTW, when did you write that paper?
At the end of 2004.
> Oh, and it is nice to see that someone from my old alma mater is being
> noticed on a games web site.
It is nice to get noticed on any web site! That Python memory
management article is the most read thing I have written.
If you have any further questions, let me know.