Re: [pyxb-users] PyXB fixes for regexps, logging and Windows

[Peter B. <pa...@us...>]

On Wed, Jul 4, 2012 at 12:20 PM, Jon Foster <jo...@jo...> wrote:
> There's one more thing I'm still trying to fix, but might not be
> ready for 1.1.5:
>
>    - I'm trying to get PyXB to be consistent about it's output.
>      Currently it's impossible to reliably reproduce PyXB bindings,
>      since PyXB seems to regularly re-order it's output and renumber
>      anonymous types.  So to get a reproducible build the generated
>      PyXB bindings have to be checked in to version control, and
>      checking in generated files isn't nice.  It's also impossible
>      to look at diffs between different versions of the bindings,
>      because there can be huge differences even if they were
>      generated from the same XSD and have the same effect.

I have to recommend holding off on this.
https://sourceforge.net/apps/trac/pyxb/ticket/112 is on the queue for
1.1.5, and the changes in generation and the content model are likely
to be really pervasive.

I sympathize with the goal in part.  Being able to check for
differences in the generated bindings is helpful during development.
I'm not immediately in favor of adding generated code to a repository
(except at a release point, where it's archival, and historical
differences should not matter).  But your comment does raise the
possibility of interchange issues with two installations from the same
schema and PyXB version if pickled files (archives or serialized data)
are involved.  I haven't thought of the ramifications of that.

I probably wouldn't merge in a change like this, mostly because it'd
conflict with #112.  Could you instead add a new ticket for this
feature, perhaps addressing problems that the lack of reproducibility
creates (other than version control), so that I keep it in mind when
doing the next update?

Thanks.

Peter