|
| 1 | +version 0.4.0 - 2012-02-14 |
| 2 | +========================== |
| 3 | + |
| 4 | +New: |
| 5 | + |
| 6 | + * Client interface methods have more explicit arguments and now take an |
| 7 | + error callback. |
| 8 | + |
| 9 | + The `provision` `notify` and `feedback` methods in v0.3.2 would |
| 10 | + implicitly assume they should perform asynchronously if the `callback` |
| 11 | + argument was supplied. They would spin off a thread, later calling |
| 12 | + the callback. |
| 13 | + |
| 14 | + Now those methods take an `async` parameter, when True, will spin off |
| 15 | + the XML-RPC request in another thread, calling `callback(result)` when |
| 16 | + complete or `errback(exception)` if an error occurred. |
| 17 | + |
| 18 | + * Clients will now automatically try to re-provision themselves if `INITIAL` |
| 19 | + was provided during configuration. This helps, in case the server goes |
| 20 | + down, to be able to retry provisioning at least once. |
| 21 | + |
| 22 | +Fixed bugs: |
| 23 | + |
| 24 | + * Fixed #21 - logging of full contents of file PEM file when providing the |
| 25 | + whole thing in `provision()` |
| 26 | + |
| 27 | + * Fixed #25 - provide a wrapper for api functions which will automaticaly |
| 28 | + try to reprovision should it encounter a `UknownAppID`. |
| 29 | + |
| 30 | +Other: |
| 31 | + |
| 32 | + * Removed some of the redundant documentation from the setup.py file. |
| 33 | + Eventually I want to move to sphynx docs. That software didn't really |
| 34 | + exist in the same capacity in 2010 as it does now. |
| 35 | + |
| 36 | +version 0.3.2 - 2010-08-05 |
| 37 | +========================== |
| 38 | + |
| 39 | +Started tracking changes. This is the version that everyone has been using for |
| 40 | +the past few years. |
| 41 | + |
0 commit comments