Thank you very much - the fix is working ;)
Now I have another question but I will start a new thread.
On Wed, Feb 27, 2013 at 10:22 PM, Peter Bigot wrote:
> The actual fix was slightly different but has the same effect on the
> bindings as what I recommended below. Details in the trac ticket
The actual fix was slightly different but has the same effect on the
bindings as what I recommended below. Details in the trac ticket.
Peter
On Wed, Feb 27, 2013 at 12:47 PM, Peter Bigot wrote:
> I've replicated this as http://sourceforge.net/apps/trac/pyxb/ticket/191
>
> In pyxb/binding/basis
I've replicated this as http://sourceforge.net/apps/trac/pyxb/ticket/191
In pyxb/binding/basis.py add 'Namespace' to the _ReservedSymbols set in the
complexTypeDefinition class.
As a consequence, the attribute "Namespace" will be spelled "Namespace_" in
the bindings, but that's consistent with ho
Actually the global Namespace should not be overriden by the local
declaration because it is local to the class - the code below the local
declaration should use the global Namespace instead of the local Namespace
One thing that comes to my mind is to have this in the bindings:
...
globalNamespace
Hi all,
Today I hit a problem while I was trying to import the generated bindings
for a particular schema. After some debugging I found out that the problem
is actually with the schema - it defines a property called "Namespace" (yep
..) and in the generated code there is something like this:
Nam
