Supports Python 2.7+ and 3.4+.
Module based on steam for interacting with Dota2’s Game Coordinator. If you’ve used node-dota2 then this module should feel right at home. Check out the documentation to get started.
Documentation: http://dota2.readthedocs.io
Contributions and suggestion are always welcome.
Installation
Install latest version from PYPI:
pip install dota2
Install the current dev version from github:
pip install git+https://github.com/ValvePython/dota2 # if you are installing over existing install # note: "only-if-needed" will only update dependecies if needed pip install -U --upgrade-strategy only-if-needed git+https://github.com/ValvePython/dota2
1 maintainer
Metadata
1 maintainer
Release files for dota2 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dota2-1.1.0.tar.gz | 451.7 kB | Without provenance | Details for dota2-1.1.0.tar.gz |
Release files / dota2-1.1.0.tar.gz
| Download URL | dota2-1.1.0.tar.gz |
|---|---|
| Size | 451.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2688d8878abde6a80b67cd445c2c9048605c19243382e38d72a5c1c0ca3b3ca8
|
|
BLAKE2b-256 checksum How to use checksums |
aa5f2dd238b1fb2f9d44727e739fda288a5da740c8dbc205b8477d999b500acc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.30.0 CPython/3.6.9
|
Security for dota2 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
