#208 base type attribute qnames resolved in wrong namespace context

[Peter A. Bigot]

When generating bindings for a type where the qname in the extension or restriction base attribute is not in scope at the containing complex type tag, the resolution of the type fails.

[Peter A. Bigot]

• status changed from new to closed
• resolution set to fixed

Fixed in following commit:

commit 64346ad532056ab3894a1f25f1c8fcdcf6aea7f1
Author: Peter A. Bigot <pab@pabigot.com>
Date:   Tue Sep 10 14:37:49 2013 -0500

    trac/208: base type attribute qnames resolved in wrong namespace context

    Add a new method to resolve an attribute with QName content to the expanded
    name immediately rather than delaying the interpretation until the point
    where type resolution is done.  Apply this to all schema attributes which
    have QName values (base, type, ref, substitutionGroup, itemType, and
    memberTypes).

:100644 100644 0b9ab37... 325c21f... M  pyxb/utils/domutils.py
:100644 100644 97c3af8... 7c3541c... M  pyxb/xmlschema/structures.py
:000000 100644 0000000... 76471af... A  tests/trac/test-trac-0208.py