Changes:
1. Added test cases for the JSON_RPC methods (not the old RPC methods)
2. Tweaked a couple of the methods to make input and output more intuitive
Instead of passing a list a specificly crafted dictionaries, you can now
just pass the ip, ban, and seconds parameters each. They can be single
elements or lists of the same size.
Changes:
1. Added a JSONRPCDaemon method for every Monero Daemon RPC Command that is not obsolete or binary.
2. Added a restricted() method to JSONRPCDaemon which returns whether the node is in restricted mode.
3. Added the ability to not pass any POST data to raw_request().
4. Added RestrictedRPC exception to monero/backends/jsonrpc/exceptions.py
5. Added a DaemonIsBusy exception to monero/exceptions.py
Motivation: I wanted to add comprehensive daemon RPC functionality to JSONRPCDaemon, which right now only
supports a handful of all the available commands. While it is possible to perform any RPC command with
raw_request() and raw_jsonrpc_request(), I wanted the user to able to know which commands are available,
what inputs the command takes, what output it gives, and leverage the command's power while knowing the
least amount of implementaton details as possible. The Monero Daemon RPC commands do not necessarily have
the most consistent and simple interface, and that is what this commit brings to the table. The new
methods also have the benefit of local input validation, which allows for fewer, more easily decipherable
bugs for the user.
Note: The vast majority of the lines in this commit are documentation. I tried to be as comprehensive as
possible.
I changed one file: `monero.backends.jsonrpc.daemon` to add one line.
This send the `"prune": True` option along with the `get_transactions` call.
The data that is pruned is not used by the `_do_get_transactions` call but
it can save up to 80% in bandwidth.