Hi Peter, I've been testing PyXB with a SAMLv2 document and run into the unimplemented base64Binary binding.
After taking a stab at implementing this binding I've realised that the reason the code is unimplemented is likely because there's no clear way to differentiate between raw binary data and a string in Python 2.x. What's the thinking around this sort of binding (where the encoded and decoded data are to all intents and purposes indistinguishable from each other)? Any thoughts on a clean approach? I'm happy to do the implementation work, but I'd like some input on the design. I'm happy to just go with an approach that insists on the data being base64 encoded prior to binding and simply checks that the encoding is valid - would this be OK as a patch? Michael
------------------------------------------------------------------------------
_______________________________________________ pyxb-users mailing list pyxb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyxb-users
