Project

Profile

Help

Is there any documented or undocumented change in SaxonC 12.3 that explains why evaluate_single in case of returning an XdmMap directly gives me a PyXdmMap instead of a PyXdmItem

Added by Martin Honnen 11 months ago

While trying to update my SaxonC HE Python powered XML workbench from 12.2 to 12.3 I had to change code that basically does evaluate_single on the XPath fn:transform function which returns an XDM map.

With 12.2 that evaluate_single call gave me a PyXdmItem on which I had to call get_map_value() to get a Python PyXdmMap.

Now with 12.3 I find I have as a result of the evaluate_single call directly a PyXdmMap.

In the end that simplifies my code but I don't see anything in the change log or change documentation explaining it.

Is there any change in the API or class hierarchy explaining it?


Replies (1)

RE: Is there any documented or undocumented change in SaxonC 12.3 that explains why evaluate_single in case of returning an XdmMap directly gives me a PyXdmMap instead of a PyXdmItem - Added by O'Neil Delpratt 11 months ago

I am finding it difficult to track down where there has been a change in this area. It is quite possible that there was an internal bug that unknowingly got fixed.

    (1-1/1)

    Please register to reply