There are two things you'll need to do.
First, see
http://pyxb.sourceforge.net/userref_pyxbgen.html#sharing-namespace-bindings
When you generate the two bindings independently as you are, you end up with
two modules for the shape namespace, the second generated implicitly because
circle depends o
Thanks for the reply. I'll try to explain with an example below, and
any help you can give would be much appreciated.
I generate the bindings like this:
$ pyxbgen -u shape.xsd -m shape
$ pyxbgen -u circle.xsd -m circle
Now the following code works (using the circle package):
from pyxb.utils
It's been a while since I've done anything with PyXB, so I may be rusty.
But what you're describing is supposed to just work.
PyXB maintains a registry of known namespaces, which is initialized when a
module is loaded. As a document is processed, the relevant namespace should
be resolved and its
