Roger Dahl

Just wanted to let you know that PyXB is currently working perfectly for us. The issues I was having with specific test run orderings giving unexpected generated XML types was due to some experimental SetDefaultNamespace() calls I had accidentally left in the code. After removing them, I now get the expected types regardless of test execution order. I've also verified that the initial issue I was having is due to the injected PyXB mixins. Thanks again!

Thank you for the info. I don't think the debugger would see the injected PyXB mixins, so that seems very like to be what's happening. I'll do a test to verify. I have also encountered an issue now where a bound object that had a namespace was serialized with a different namespace depending on the order in which the tests ran. In both cases, I seem to have gotten things working by adding pyxb.utils.domutils.BindingDOMSupport.SetDefaultNamespace(None) before the call to toxml() (at least for the ordering...

Thank you for your fast reply, Peter, and my appologies for not replying in any timely...

Thank you for PyXB. I'm having trouble getting PyXB working with multiprocessing...

Thank you for the help, Peter. Your solution is working out nicely so far.

I first posted this question on Stack Overflow. Trying again here... I have generated...