This is likely due to another bug in pyArango. https://github.com/ArangoDB-Community/pyArango/issues/160
Bug introduced after latest release on pypi, probably resolved by using release instead of upstream git. The changes desired have been merged, latest release was last September and merges occurred in March.
remingtonc
commented
4 years ago
This is likely due to another bug in pyArango. https://github.com/ArangoDB-Community/pyArango/issues/160 Bug introduced after latest release on pypi, probably resolved by using release instead of upstream git. The changes desired have been merged, latest release was last September and merges occurred in March.