Claudio Sparpaglione

As per description

Unit tests failing on Travis CI: https://app.travis-ci.com/github/csparpa/pyowm/builds/249771377 Branch: develop Module: `tests.unit.airpollutionapi30.test_airpollution_client.TestAirPollutionHttpClient` ```shell # extract from Travis CI build log ====================================================================== FAIL: test_get_coi (tests.unit.airpollutionapi30.test_airpollution_client.TestAirPollutionHttpClient) ---------------------------------------------------------------------- Traceback (most recent call last): File...

If you need to access forecaster's `will_have_storm()`, `will_have_hurricane()`, etc., which one_call doesn't give access to (as far as I could find) but don't care about the frequency, "3h" instead of...

Distribute PyOWM via package managers to the most used Linux distributions

14

In order to make even more straightforward for users to install PyOWM, it would be superb to have it installable via package managers (such as `apt` or `rpm`) on the...

Have a look here https://agromonitoring.com/price and see what needs to be done. Very likely, the old PyOWM methods will need to be adapted to work the polygon-based way

https://agromonitoring.com/api/history-ndvi

Document purpose for all assertion methods

6

Each assertion method should clearly document its purpose. As the return values for each assertion method can either be the `Check` object instance itself or an exception and each method...

Unit test all assertion methods

7

Ideally, test coverage of assertion methods (eg. `is_none(), is_not_none()`, etc.) should be 100%

Fix is_callable and is_not_callable behaviour

2

Classes are also callable - not only functions

Go on with implementing assertion methods listed on README.md

2

As per title Each new assertion method should: - have a companion "negated" assertion method. If you implement `is_xyz()` method, then you should also implement a `is_not_xyz()` method alongside -...