Remove dependency on future

[apmorton]

from past.builtins import basestring causes DeprecationWarning
PythonCharmers/python-future#551

I believe this alternative using six should behave identically.

On python3 past.builtins.basestring is equivalent to (bytes, str):
https://github.com/PythonCharmers/python-future/blob/80523f383fbba1c6de0551e19d0277e73e69573c/src/past/types/basestring.py#L26

On python2, it is the built in basestring:
https://github.com/PythonCharmers/python-future/blob/80523f383fbba1c6de0551e19d0277e73e69573c/src/past/builtins/__init__.py#L52

six.string_types is either (basestring, ) or (str, ):
https://six.readthedocs.io/#six.string_types

six.binary_type is either str or bytes:
https://six.readthedocs.io/#six.binary_type

[apmorton]

@dariosky can anyone look at this please?

[dariosky]

Hi @apmorton, thank you for your patience.
The team will check and let you know as soon as possible.

[apmorton]

Anybody? It's been a year now...

@joserc87 @dariosky

[joserc87]

Hi @apmorton, sorry for the delay. I've had a look and the changes seem ok, except for one example where we still require "future" (from concurrent.futures.thread import ThreadPoolExecutor in ravenpack_annotations_batch.py). I added a note in that example saying that we require either python 3.2+, or if someone is still using 2.7, they can install the futures package to run the example.
Merging

[apmorton]

Great, thanks!

Any ETA on publishing a new version with these fixes to pypi?

[joserc87]

Most likely, in a few days

[joserc87]

It's now part of release https://github.com/RavenPack/python-api/releases/tag/v1.1.1. Feel free to do a pip install --upgrade ravenpackapi or poetry or however you manage the dependencies :)