#82 restore binding style support

[Peter A. Bigot]

Attempts to configure the accessor binding style raise an exception, though in fact the code works. Ability to configure code generation needs to be implemented

[Peter A. Bigot]

Proposed approach: The parameter to --binding-support is the name of a module, which presents a defined interface that can be used to identify the key template parameters (inspector, mutator, appender, etc.) and the templates themselves for attribute and element declarations within a complex type definition. Standard implementations that support the property and accessor styles will be present in pyxb.binding.style.*. Users can implement their own styles as long as they conform to the defined interface.

[Peter A. Bigot]

• milestone changed from PyXB 1.1.2 to PyXB 1.1.3

[Peter A. Bigot]

• milestone changed from PyXB 1.1.3 to PyXB 1.1.4

[Peter A. Bigot]

• priority changed from major to minor
• status changed from new to accepted
• milestone changed from PyXB 1.1.4 to PyXB 1.1.5

At this point, the resolution to this is likely to be "won't fix".

[Peter A. Bigot]

• status changed from accepted to closed
• resolution set to wontfix

commit 8ef6f9846a7d5829f5955f22294b0d336554fe1c
Author: Peter A. Bigot <pabigot@‌>
Date: Fri Jun 15 18:19:12 2012 -0500

trac/82: restore binding style support

Won't fix.

Too much existing code would become unusable if elements and attributes were
manipulated through accessors instead of properties. This would create a
fundamental portability issue between PyXB modules. Should an alternative
interface be desired, it should be done by providing a new generator in a
system that is called "MetaPyXB" or something like that.