Sebastian Meiling

fix: cleanup imports of python-magic and IntelHex

3

Moving optional imports of python-magic and IntelHex inline, with error handling. Omitting state variables for cleaner code and better readability.

feat: adapt code to pass flake8

2

this modifies the code to pass standard flake8 static code checks and its that to travis config as well. **NOTE** this depends on #93 and should not be merged before

docs: add readthedocs doxygen wrapper

4

addressed #118 This may need some work. Currently it shows (lots of) errors during generation, and the output is single-page -> hence, a bit unstructured.

rtrlib/transport: change port from int to char in ssh transport

1

This addresses #80 and applies comment by @shaddeus so that both `struct tr_tcp_config` and `struct tr_ssh_config` handle port as `char *`. However, now the tcp config is just a subset...

inconsistent port attribute in structs tr_tcp_config and tr_ssh_config

10

I just stumbled over a weird inconsistency, `tr_tcp_config` is defined as: ``` struct tr_tcp_config { char *host; char *port; char *bindaddr; }; ``` and `tr_ssh_config` as: ``` struct tr_ssh_config {...

add a parameter like `range` (list|tuple) of allowed values or min and max values which could also be used for testing, i.e. humidity or percentage would have an allow range...

Though basic tests are in place to provide an overall good code coverage, not all data types are tested thoroughly for edge cases, i.e. minimal and maximum values and such....

Add and update documentation

1

- should write some documentation on supported data types - maybe some more (extended) usage examples - also check/test interop with other libs and packages from different languages

add inter-op tests

2

Currently test are only run with and against pycayennelpp, this is insufficient. We should run encoding and decoding tests against other libs from other programming languages to ensure interoperability, as...

fix Python updateprogress()

3

According to the [documentation](https://octopus.com/docs/deployments/custom-scripts/logging-messages-in-scripts) the message for updateprogress in Python scripts is optional. However, when a message is not provided the script fails because the default for message is None...