Great news :)

I'm looking forward to your bugfix.


On Wed, Mar 5, 2014 at 4:44 PM, Peter Bigot <> wrote:
Heh.  tns should not be special.  It is special because PyXB has not properly handled the QName type until you pointed this out: the value space and lexical space are not the same.  Since the schema for soap12 identifies the enumeration restrictions with the string "tns:Sender" it works.  Once I correct PyXB to handle QName properly (making the type inherit from ExpandedName instead of string), alternative namespace prefixes will also work.

This is now and I should get a patch into the next branch by the end of the week.


On Wed, Mar 5, 2014 at 9:25 AM, Xavier Fernandez <> wrote:
Hello list,

I'm quite new to PyXB and I'm looking forward for the porting to Python 3.

Meanwhile I've got an issue with soap 1.2 faults, is the 'tns' namespace magic or something ?:

from pyxb.bundles.wssplat import soap12

resp="""<{0}:Envelope xmlns:{0}="">
            <{0}:Reason><{0}:Text xml:lang="en">Reason test</{0}:Text></{0}:Reason>

print 'OK for tns'

The CreateFromDocument works with 'tns' but not with 'anything' that fails with:
pyxb.exceptions_.SimpleFacetValueError: Type {}faultcodeEnum enumeration constraint violated by value anything:Sender

Am I missing something ?


Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
pyxb-users mailing list