#146 mark encoding in generated output

[Peter A. Bigot]

When PyXB writes a binding module, it uses the utf-8 encoding, but does not indicate this in the header. It should do so.

[Peter A. Bigot]

• status changed from new to closed
• resolution set to fixed

commit 791fc4707b6eca9e7f731007a28e25ef5fea06b5
Author: Peter A. Bigot <pabigot@‌>
Date: Wed Jun 13 22:12:53 2012 -0500

trac/146: mark encoding in generated output

Add global values for the input and output encodings to the top-level pyxb
module, rather than hard-coding them throughout the source.

Add the output encoding used by the generation module to the top of the
generated python module.

Literal uses of specific encodings are left for pickling and for hash
calculation. All other uses should reference the global values for now;
when trac/145 is addressed the information should derive from the encoding
of the schema or some other source.