Potential dependency conflicts between binance-db and chardet

[NeolithEra]

Hi, as shown in the following full dependency graph of binance-db, python-binance requires chardet * ， while the installed version of requests(2.22.0) requires chardet <3.1.0,>=3.0.2.

According to Pip's “first found wins” installation strategy, chardet 3.0.4 is the actually installed version.

Although the first found package version chardet 3.0.4 just satisfies the later dependency constraint （chardet <3.1.0,>=3.0.2), it will lead to a build failure once developers release a newer version of chardet.

Dependency tree--------

binance-db - 0.0.2
| +- psycopg2-binary(install version:2.8.4 version range:*)
| +- python-binance(install version:0.7.4 version range:*)
| | +- autobahn(install version:19.11.1 version range:*)
| | | +- cryptography(install version:2.8 version range:>=2.7)
| | | +- six(install version:1.13.0 version range:>=1.11.0)
| | | +- txaio(install version:18.8.1 version range:>=18.8.1)
| | | | +- six(install version:1.13.0 version range:*)
| | +- certifi(install version:2019.9.11 version range:*)
| | +- chardet(install version:3.0.4 version range:*)
| | +- cryptography(install version:2.8 version range:*)
| | +- dateparser(install version:0.7.2 version range:*)
| | | +- python-dateutil(install version:2.8.1 version range:*)
| | | +- pytz(install version:2019.3 version range:*)
| | | +- regex(install version:2019.11.1 version range:*)
| | | +- tzlocal(install version:2.0.0 version range:*)
| | | | +- pytz(install version:2019.3 version range:*)
| | +- pyOpenSSL(install version:19.1.0 version range:*)
| | | +- cryptography(install version:2.8 version range:>=2.8)
| | | +- six(install version:1.13.0 version range:>=1.5.2)
| | +- requests(install version:2.22.0 version range:*)
| | | +- certifi(install version:2019.9.11 version range:>=2017.4.17)
| | | +- chardet(install version:3.0.4 version range:<3.1.0,>=3.0.2)
| | | +- idna(install version:2.8 version range:>=2.5,<2.9)
| | | +- urllib3(install version:1.25.6 version range:<1.26,>=1.21.1)
| | +- service-identity(install version:18.1.0 version range:*)
| | | +- attrs(install version:19.3.0 version range:>=16.0.0)
| | | +- cryptography(install version:2.8 version range:*)
| | | +- ipaddress(install version:1.0.23 version range:*)
| | | +- pyasn1(install version:0.4.8 version range:*)
| | | +- pyasn1-modules(install version:0.2.7 version range:*)
| | +- six(install version:1.13.0 version range:*)
| | +- Twisted(install version:19.10.0 version range:*)
| | +- urllib3(install version:1.25.6 version range:*)
| +- sqlalchemy(install version:1.3.10 version range:*) 

Thanks for your attention.
Best,
Neolith

[NeolithEra]

Suggested Solution

1. Ask your upstream project python-binance to fix his direct dependencies to be chardet <3.1.0.
2. Ask your upstream project requests to lose the version range of chardet to be >=3.0.2.

@StoicPerlman Which solution do you prefer, 1 or 2?
Please let me know your choice. May I pull a request to solve this issue?