Dear Dave Thanks for incorporating this into 2.18a!
With regards to your question: On 16 Dec 2015, at 18:26, Dave Kuhlman <dkuhl...@davekuhlman.org> wrote: > > Your change (below) seems like a good one to me. I've patched that > into my repository. It will be uploaded soon. > > Thanks for your fix. > > However, this mystified me for awhile. I parsed and exported a file > (see attached schema and XML instance doc) and could not reproduce > the problem, at first. Then I found out that when the generated > code parses the instance doc, it saves the value as a string (e.g. > "0.0"). It's only after you set the value to *numeric* zero, that > the problem appears. > > Which makes me wonder whether the value of something defined as > xs:simpleContent that extends type xs:float (or xs:integer or other > numeric types) should be converted to a Python int or float by the > build method. But, that might cause disruption for existing > applications and users. So, I suppose that is a change for another > time, if at all. > > What do you think? >From my perspective - conversion to int/float would not be disruptive. There >may be a few instances where I may need to remove redundant conversion etc but >I would not mind doing that. However I am mindful that this may have >consequences for other applications so it would be good to hear from other >users as well. Many thanks and best wishes Ardan > ------------------------------------------------------------------------------ _______________________________________________ generateds-users mailing list generateds-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/generateds-users
