This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients docs@python, eric.araujo, ezio.melotti, fdrake, loewis, pitrou, scoder
Date 2011-11-29.15:26:35
SpamBayes Score 9.68889e-10
Marked as misclassified No
Message-id <>
> Seriously, minidom is widely known for being extremely slow and 
> extremely memory hungry. And that is backed by basically any benchmark 
> that has ever been done on the subject.

Do you have any link?
My point is that if you say thing like "significantly/several times higher memory footprint than X" you are basically scaring the users away from the module.  If for an average documents it takes, say, 30-50MB of memory, it seems perfectly reasonable to me, even if ElementTree takes 3-5MB.  I would actually consider 100-200MB still ok too, unless I have to parse lot of documents or I'm running low of memory for other reasons.
Date User Action Args
2011-11-29 15:26:35ezio.melottisetrecipients: + ezio.melotti, loewis, fdrake, pitrou, scoder, eric.araujo, docs@python
2011-11-29 15:26:35ezio.melottisetmessageid: <>
2011-11-29 15:26:35ezio.melottilinkissue11379 messages
2011-11-29 15:26:35ezio.melotticreate