Prune Common Functionality From Bindings about python-cybox HOT 3 CLOSED

If it's code in the bindings that we've had to modify, then I agree. This will also help whenever we have to regenerate the bindings (when a new version of CybOX is release, for example). But if it's purely to reduce duplicative code auto-generated by GenerateDS (which produces lots of duplicative code), then I'm not sure it's worth the effort. It will make the final package a bit smaller, but not reduce the amount of maintentance we have to do.

from python-cybox.

That common code changes a lot between releases of GenerateDS so we can't really tuck it away and reference it later on. We would probably need to go through the process of pulling it out into a common module with each release of the bindings/apis, and modify the bindings to refer to the common module each time. Basically, this is going to create more work for us with each release with little benefit.

Because this is purely to remove duplicative code, will need to be done with each release, and requires us to spend more time altering/updating the bindings I don't think we should invest development time and effort on this.

from python-cybox.

Agree with both of you. There are several ways to solve this, but all require a fairly significant time investment for little payoff besides slightly smaller file sizes.

from python-cybox.