Hi,
Stefan Behnel behnel_ml@gkec.informatik.tu-darmstadt.de schrieb am 23.06.2006 14:31:20:
True. I just changed that and adapted the doctests to the new API.
http://codespeak.net/svn/lxml/trunk/doc/namespace_extensions.txt
I think a better API would be an explicit module level function for
setting the default element class.
The nice thing about staying close to the existing solution is that it
is
still possible to have per-tagname-registered custom element classes,
if
you wish.
That's not a problem. Namespace specific classes obviously override the
global
default class, just as they already do for _Element.
Stefan
I meant that it was possible to have namespace-agnostic, per-tagname custom default classes (as opposed to namespace-aware per-tagname custom classes), but admit I don't really have any usecase for that. More of a side-effect of making just a minimal code change, to learn the workings.
And admittedly your solution and API is nice and clean.
You guys are really fast!
Thanks, Holger
Der Inhalt dieser E-Mail ist vertraulich. Falls Sie nicht der angegebene Empfänger sind oder falls diese E-Mail irrtümlich an Sie adressiert wurde, verständigen Sie bitte den Absender sofort und löschen Sie die E-Mail sodann. Das unerlaubte Kopieren sowie die unbefugte Übermittlung sind nicht gestattet. Die Sicherheit von Übermittlungen per E-Mail kann nicht garantiert werden. Falls Sie eine Bestätigung wünschen, fordern Sie bitte den Inhalt der E-Mail als Hardcopy an.
The contents of this e-mail are confidential. If you are not the named addressee or if this transmission has been addressed to you in error, please notify the sender immediately and then delete this e-mail. Any unauthorized copying and transmission is forbidden. E-Mail transmission cannot be guaranteed to be secure. If verification is required, please request a hard copy version.