Fwd: Re: Python's memory hogging

[Werner]

Noticed this message/thread on the pylons list.

Would Amara help in this situation?

Werner

-------- Original Message --------

Subject:	Re: Python's memory hogging
Date:	Sun, 6 May 2012 19:14:29 -0600 (MDT)
From:	John W. Shipman <jo...@nmt.edu>
Reply-To:	pylons-...@googlegroups.com
To:	pylons-...@googlegroups.com
CC:	John Shipman <jo...@nmt.edu>

On Mon, 7 May 2012, Graham Higgins wrote:

+--
| (deletia)
| The discussion on the issue ticket associated with the commit:
|
| http://bugs.python.org/issue11849
|
| contains further details, including an example of exactly how creating
                                                                ^^^^^^^^
                                                                ^^^^^^^^
                                                                ^^^^^^^^
| large XML files in Python might cause the memory retention via lingering
| refs --- just as Ben describes.
|
| AIUI, the standard approach to handling large XML files is to use a
| stream processor such as SAX.
+--

Since when does SAX have an OUTPUT option?!  I just looked at
www.saxproject.org, and it seems to be all about reading.

If somebody has a nice general solution to *generating* large XML
files, as opposed to reading them, I'd love to hear it.  I have
an application that builds a large HTML table from a database.
I'm currently using lxml (which is an ElementTree variant), and
it's limited by the memory available on the server.

I supposed I could roll my own low-memory XML generator,
but I can't believe no one has done this already!

Best regards,
John Shipman (jo...@nmt.edu), Applications Specialist, NM Tech Computer Center,
Speare 146, Socorro, NM 87801, (575) 835-5735, http://www.nmt.edu/~john
  ``Let's go outside and commiserate with nature.''  --Dave Farber

-- 
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
To post to this group, send email to pylons-...@googlegroups.com.
To unsubscribe from this group, send email to pylons-discus...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.