#101 need facility to customize reserved symbols

PyXB 1.3.0
accepted
None
Binding model
major
PyXB 1.1.2
defect
2013-09-18
2011-05-21
No

PyXB deconflicts XML symbols from Python reserved words (like "class") and from attribute identifiers that PyXB uses (like "value" and "content"). It does not deconflict symbols that Python might use but that are not reserved, such as "str", "list", and "property". Thus XML elements and types with these names may create conflicts

PyXB should not be obliged to guess every identifier that might have a global use, so it needs a way for the developer to extend the reserved symbols list when generating bindings for a schema.

Discussion

  • Peter A. Bigot

    Peter A. Bigot - 2011-09-09
    • milestone changed from PyXB 1.1.3 to PyXB 1.1.4
     
  • Peter A. Bigot

    Peter A. Bigot - 2012-06-14
    • milestone changed from PyXB 1.1.4 to PyXB 1.1.5
     
  • Peter A. Bigot

    Peter A. Bigot - 2012-08-30
    • milestone changed from PyXB 1.1.5 to PyXB 1.2.0
     
  • Peter A. Bigot

    Peter A. Bigot - 2012-11-08
    • milestone changed from PyXB 1.2.0 to PyXB 1.2.1
     
  • Peter A. Bigot

    Peter A. Bigot - 2012-12-17
    • milestone changed from PyXB 1.2.1 to PyXB 1.2.2
     
  • Peter A. Bigot

    Peter A. Bigot - 2013-04-17
    • milestone changed from PyXB 1.2.2 to PyXB 1.2.3
     
  • Peter A. Bigot

    Peter A. Bigot - 2013-09-18
    • status changed from new to accepted
    • milestone changed from PyXB 1.2.3 to PyXB 1.3.0
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks