#204 fixed elements improperly create non-empty default

PyXB 1.2.3
Binding model
PyXB 1.2.2

See: https://sourceforge.net/p/pyxb/discussion/956708/thread/b6c1884d

When #99 was fixed the reset value for an element was changed to the default values of its element content; prior to that element content was reset to None. The new reset doesn't take into account that a non-empty element may not be valid.

1 Attachments


  • Peter A. Bigot

    Peter A. Bigot - 2013-07-24
    • status changed from new to closed
    • resolution set to fixed
    • milestone set to PyXB 1.2.3

    Fixed in following commit on next branch.

    commit f30dcf8d1129de3d4bfc1fa2fda58394ebc0e92b
    Author: Peter A. Bigot <pab@pabigot.com>
    Date:   Wed Jul 24 10:25:59 2013 -0500
        trac/204: fixed elements improperly create non-empty default
        Distinguish the reset value of an element from its default value, and use
        its reset value when creating new instances.  This restores the behavior
        prior to the fix for trac/99, so is a reversion from a "feature" of
        PyXB-1.2.1, but that "feature" was a premature and incomplete solution to
        trac/170 so it's best to remove it.
    :100644 100644 164a23f... bba26a4... M  pyxb/binding/content.py
    :100644 100644 e2c0171... 1e45b4b... M  tests/trac/test-trac-0099.py
    :000000 100644 0000000... 4b74c8c... A  tests/trac/test-trac-0204.py

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

Sign up for the SourceForge newsletter:

No, thanks