Dear Stefan!
Am 03.03.22 um 23:54 schrieb Stefan Behnel:
Hi Volker,
this reads like something you could implement on top of lxml.objectify, via
subclassing and an appropriate element class lookup.
This could really be a plain Python package that you could distribute on PyPI
to give users an easy choice which interface they prefer. Not everything needs
to be part of lxml itself.
My prototype is still clued to lxml since I use internal cython
functions of lxml that are not exported to python space. But with a
little help of the kind lxml people it may be possible to completely
seperate it from lxml.
Cheers,
Volker
--
=========================================================
inqbus Scientific Computing Dr. Volker Jaenisch
Hungerbichlweg 3 +49 (8860) 9222 7 92
86977 Burggenhttps://inqbus.de
=========================================================
_______________________________________________
lxml - The Python XML Toolkit mailing list -- lxml@python.org
To unsubscribe send an email to lxml-le...@python.org
https://mail.python.org/mailman3/lists/lxml.python.org/
Member address: arch...@mail-archive.com
