Client PIP Requirements about dotaservice HOT 5 CLOSED

Also, additionally the requirements.txt could cover all the env variables that must be set to run the code.

STEAM_ID, STEAM_PWD, GOOGLE_APPLICATION_CREDENTIALS, etc

from dotaservice.

if you add all dependency in client.py, the package will be very heavy, since PyTorch is included.
it is good to keep the minimal dependency, since it is 'dotaservice' not 'dotaclient'

from dotaservice.

I mean just listing them in a file so you can run ‘pip install -r filename’ and be done rather than rerunning the client numerous times and waiting for exception to be thrown when module not found.

from dotaservice.

separate requirements.txt for client.py is good, but never pollute the requirements.txt for package installation

from dotaservice.

requirements file is ok..
I think the examples should maybe be refactored entirely, it's growing into a lot more than an example. I also want to stay agile and make some friday-afternoon decisions on examples, and I dont want to block you guys. I am not sure how we deal with that.
The dotaservice itself is different: that should just be rocksolid with few api changes.

from dotaservice.