The downside is that values like:
x=1 y=2
Must be edited or your model cannot be read:
x=1; y=2
The upside is that you can use full Python expressions, so ints come in as ints (instead of strings) and you can create lists and so on:
Samples=[1, 2, 3]
Which was the motivation for this change.
obj.setSomeBool('s') # raises TypeError
Some numeric compatibility is allowed:
The date, time and datetime accessors no longer accept strings (such as '2001-01-15') if you have an mx.DateTime.
For value checking:
Also, MiddleKit assumes that if you have DateTime, it is in the mx package, as in:
from mx import DateTime