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
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
Dear Stefan!
Am 03.03.22 um 20:05 schrieb Stefan Behnel:
So … I think keeping prefixes generally out of the interface is a good
decision.
I share your sorrows. Therefore I never even thought of changing the
behavior of LXML - or even that of lxml.objectify. I will come up with
Dr. Volker Jaenisch schrieb am 03.03.22 um 18:19:
Therefore I am currently working on enabling LXML to have _
properties in objectify. The changes are not too complicated since the
source code quality is good. I am hopeful that after the weekend I will
have full functional prototype.
As
Hi,
Stefan wrote:
> Note that the content of the XML file that your code is designed to process
> did not
> change at all. It's just that some entirely unrelated content was added, in a
> completely different and unrelated namespace. And it was just externally added
> to the input data, or maybe
