-
So now that we're on the topic of requirements (#15, #19) -- I'm not sure using `future` in a library like this (esp. `future.standard_library.install_aliases()`) is a good idea.
I mean, just importi…
-
The requirements are pinned to the exact version as it is, which makes it hard to use `pip-tools` or another dependency manager.
Instead of
```
future==0.14.3
mock==1.0.1
requests==2.6.0
responses==…
-
The Server.get_public_ip method at https://github.com/UpCloudLtd/upcloud-python-api/blob/master/upcloud_api/server.py#L331 currently prefers IPv4 addresses making fetching a public IPv6 address hard.
…
-
This feature allows setting up servers on different hosts for increased redundancy.
-
The API has a hard dependency on `py.test` -- consumers of the library will thus download `py.test` (and `py`, as a transitive dependency) whenever they `pip install` it.
Unless the library does actu…
-
UpCloud has released API v.1.2 with IPv6 support. However, this client only supports v1.1 at the moment.
https://www.upcloud.com/static/downloads/upcloud-apidoc-1.2.0.pdf
-
The offline tests are lacking in numerous ways and can only reveal bad programming mistakes.
Automatic tests against the actual API would be a huge plus.