Anthony Mahanna

Issue is not solved as of [0ac6f9d](https://github.com/ArangoDB-Community/python-arango/pull/208/commits/0ac6f9d5010df84bec51282f62fd0c503e49c491)

> You should be able to put it in MANIFEST.in to make sure it is included. I currently have `global-include *.typed` in the `MANIFEST.in`, it seems to be recognized since...

Update: not solved as of https://github.com/ArangoDB-Community/python-arango/pull/208/commits/114fb44f512a6786160a19e81d79b620fba3ab37

Hey @joowani, just wondering if this is something you've come across before and considered?

> It seems that the examples provided by @finnmglas are down, showing "resource not found". @WenjieDu Looks like the route changed - adding `v2/` to the path seems to fix...

@WenjieDu So the `static.pepy.tech` API allows you to abbreviate the number with the `units=abbreviation` query parameter [](https://pepy.tech/project/requests) ``` [](https://pepy.tech/project/requests) ``` But unfortunately I am not sure how this query parameter...

Closing this issue as Active Failover has been deprecated in favour of using [cluster deployments](https://docs.arangodb.com/stable/deploy/cluster/): https://docs.arangodb.com/stable/release-notes/deprecated-and-removed-features/

hey @apetenchea could I get your thoughts on this (PR description) ^ wondering what the best way to proceed is

@apetenchea I can get behind this change, but it raises the question of what should we do with [formatter.py](https://github.com/ArangoDB-Community/python-arango/blob/main/arango/formatter.py), as that is what is currently driving the `snake_case` to `camelCase`...

@apetenchea agreed! moving forward with this will give us a chance to get community feedback