planet-client-python
planet-client-python copied to clipboard
planetlabs
Python client for Planet APIs
**Expected behavior** When testing tools for the Orders API, I'd expect the tool name and the parameters to be validated. **Actual behavior (describe the problem)** When testing tools for the...
test expected functionality for the following data api search functions, test will be skipped as they will initially fail. * list_searches * delete_search * get_search * update_search * run_search related...
Go through the unit tests and replace `Mock()`/`monkeypatch` pattern with `unittest.patch` ### Example Change this: ``` @pytest.mark.parametrize( "pretty,expected", [(False, '{"key": "val"}'), (True, '{\n "key": "val"\n}')]) def test_cli_echo_json(pretty, expected, monkeypatch): mock_echo...
This raises block has two function calls. So it will pass even if one of the functions does not raise the error. These functions should be checked in two separate...
Importing OrdersClient and/or DataClient via `from planet import OrdersClient` produces a warning, even though it works fine: 
The signature of the AuthType interface should include the write() method so that basic authentication one-liners don’t give a warning, like this one: 
Allow `planet orders create` to take text as an input. Example: ``` planet orders create {"name": "test_order", "products": [{"item_ids": ["20200922_183724_23_106a", "20200922_183722_17_106a"], "item_type": "PSScene4Band", "product_bundle": "analytic"}]} ``` Blocked by #519
When I was making the quickstart in #472 I was struck how many options I needed to supply to create an order: ``` $ planet orders create --name my-first-order --id...
implement the following item functions in the SDK * get_item * get_item_type * list_item_types #501 depends