On 02/04/13 21:14, azurIt wrote:
Hi Burak,
very cool, thank you!
I'm, currently, using Integer and Float everywhere so i will, probably, fix
that. Why exaclty is usage of spyne.model.primitive.Integer not recommended?
Dear Azur,
If your code is working with Floats, and you're happy, just don't touch
it. But remember that it's machine dependent and not really predictable
enough to do things like monetary operations.
As for the Integer type, I'm not recommending it either because it's
arbitrary-size. Any integer, even million-digit ones, will pass
validation. You most probably don't need that and need something like
Integer32 instead. I'm sure you have a database behind your services
and, for example, most of the numeric primary keys there are either 32
or 64-bit unsigned integers.
Don't know if it's bug or not but there a code without highlighting:
http://spyne.io/docs/2.10/manual/03_types.html#primitives
Well, thanks for pointing it out, but that document is going to get
probably a couple dozen more revisions -- I got a lot more to write. I'd
be glad if you'd just fix it and send a pull request.
Btw, maybe something like 'references' should be added to spyne.io so everyone
can see that spyne is really production-ready :)
I also had the idea, you're right :) I think it's called "testimonials".
Send them over people :)
best,
burak
_______________________________________________
Soap mailing list
[email protected]
http://mail.python.org/mailman/listinfo/soap
