new features
* Options added for client and server instance, to disable strict date and time check by PyRFC, before writing to data container. Options `check_date` and `check_time` are `True` by default, thus the strict checking is by default enabled, because of backwards compatibility. With these option(s) deactivated, Python server will accept any date and/or time string sent by ABAP system, even when out of standard range, like `240000`. See issue 336 for more details and PyRFC documentation.
* Server instance configuration exposed as`option` read-only property
bug-fixes
* 336 Issue with TIMS data type conversion fixed by using new `check_time` server option set, to `False`
enhancements
* Automated tests of server bindings
* Type check of connection parameters' values
documentation
* Build section updated
* New options documented