[lxml-dev] 2.1beta questions: objectify.XML, objectify.parse base_url arg, deprecate enableRecursiveStr, etree.tounicode()

[Holger Joukl]

Hi,

 I  guess the module functions XML() and parse() should also support the 
base_url arg?

Also, I suppose enableRecursiveStr() could be removed? 


 
Btw I realized that etree.tounicode() is bound to be deprecated in favor of 
tostring(..., encoding=unicode).

I suppose this is owed to ElementTree API compat which doesn't have 
tounicode() - or is this a py3k issue? 

 IMHO unicode is not an encoding and from my experience it confuses people 
starting out with unicode to 

think of unicode as an encoding. That said, I rather like the 
tostring()/tounicode() distinction API-wise, if 

purely for documentational purposes. 

 I'm not at all questioning the possibility to produce a unicode 
serialization of an XML tree: 

This is really helpful in lxml as it enables one to fallback to python 
encoding capabilities if libxml2 does not support 

some intended target encoding.

 Holger 

 

 


-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://codespeak.net/pipermail/lxml-dev/attachments/20080701/888dbe25/attachment.htm