globocom/globonetworkapi-client-python

Python client for GloboNetworkAPI

GloboNetworkAPI python client

This project is the python implementation of a GloboNetworkAPI client library.

Installation

Install the project by running:

$> pip install GloboNetworkAPI

Contributing

We are not stringent with contributions. Just fork, modify, write tests and send us a Pull Request :)

For development purpose, setup your environment by installing project and development dependencies:

$> make setup

Testing

Tests are divided into Integration, Functional and Unit tests. They are located inside tests directory. To run tests, first install tests dependencies by running:

$> make test_setup

It will download and run GloboNetworkAPI using vagrant. After that, just run the tests using:

$> make test

Releasing new version

Before releasing new version, don't forget to update the version you want. After this, run:

$> make publish

You can not upload the same version twice.

globonetworkapi-client-python's Issues

Create call to change VIP persistence methods

Need the client part of issues 18 in GloboNetworkAPI.
globocom/GloboNetworkAPI#18

Add an .editorconfig

define and maintain consistent code styles between team members working on the same code as well as between different editors and IDEs that they might use.

Loosen the version constraint of requests to avoid dependency conflicts

Hi, GloboNetworkAPI-client-python locked the version constraint of requests as requests=2.10.0, which leads to a troubling scenario that its direct downstream project ['tsuru-hm','database-as-a-service'] has to lock requests.

Could you please loosen the version constraint of requests?
Benefit of this is that users using both of ['tsuru-hm','database-as-a-service'] and requests can upgrade their third party libraries in a timely manner to reduce technical debts.

Solution

The dependency trees of your project and affected downstream projects are shown as follows.
Taking the version constraints of upstream and downstream projects into comprehensive consideration, you can

1. Loosen requests=2.10.0 to be requests>=2.10.0.
2. Loosen requests=2.10.0 to be requests==*.
3. Try to add an upper bound for requests’ version constraint, according to your compatibility.

@laurapanzariello Please let me know your choice. I can submit a PR to fix this issue.

Thanks for your attention.
Best,
Neolith