Peter A. Bigot

As best I can tell PyXB correctly supports timezones for `xsd:date` instances and provides it through [xsdRecoverableTzinfo](https://pabigot.github.io/pyxb/pyxb.binding.html#pyxb.binding.datatypes.date.xsdRecoverableTzinfo). Offhand it looks like this is a bug, but due to #100 this...

You can probably do something with [binding customization](https://pabigot.github.io/pyxb/userref_pyxbgen.html#customizing-binding-classes), by customizing the interaction with whatever element has that restricted content.

For an element containing: you would specialize the containing element, and in particular how it handles the `TEMPLATE` member. Or something like that. If the containing element is an unnamed...

I'm afraid this enhancement doesn't particularly interest me personally, so I can't provide much support towards completing it. I personally haven't used XML or Python for anything in about five...

The changes look reasonable and likely to benefit users. However, I really don't have the time or interest necessary to merge them or, more importantly, undertake to resolve any issues...

Yes; since the previous release PyPI disabled the ability to correct metadata attributes including associated version after uploading a package. I'll try to fix it in the next update, whenever...

Nothing is obvious to me. I'll take a look when I'm next working PyXB.

There's no simple way to work around this. The explanation can be found at: https://github.com/pabigot/pyxb/blob/14737c23a125fd12c954823ad64fc4497816fae3/pyxb/binding/facets.py#L404 Basically the value has already been converted to a Python dateTime instance at the point...

Given #100 and the fact the `@todo` was introduced on 2009-09-06 I think we can say it's not on the roadmap. Thanks for using PyXB and for your report. I'll...

This can be trivially reproduced by modifying `examples/amqp_publish` to use a non-existent exchange (e.g. `"amqp.direct"`). Invoked with: ``` amqp_producer server 5672 1 10 ``` the server returns a `Channel.Close` message...