Forum Rules

  • No flaming or derogatory remarks, directly or through insinuation.
  • No discussion, sharing or referencing illegal software such as hacks, keygen, cracks and pirated software.
  • No offensive contents, including but not limited to, racism, gore or pornography.
  • No excessive spam/meme, i.e. copious one liners in a short period of time, typing with all caps or posting meme responses (text/image).
  • No trolling, including but not limited to, flame incitation, user provocation or false information distribution.
  • No link spamming or signature advertisements for content not specific to Dota 2.
  • No Dota 2 key requests, sell, trade etc.
  • You may not create multiple accounts for any purpose, including ban evasion, unless expressly permitted by a moderator.

  • Please search before posting. One thread per issue. Do not create another thread if there is an existing one already.
  • Before posting anything, make sure you check out all sticky threads (e.g., this). Do not create new threads about closed ones.
  • It is extremely important that you post in correct forum section.

  • Balance discussion only in Misc.
  • All art related (such as hero model) feedbacks go to Art Feedback Forum.
  • All matchmaking feedback should go here: Matchmaking Feedback
  • All report/low priority issues should go here: Commend/Report/Ban Feedback
  • No specific workshop item feedback. These should go to workshop page of that item.
  • When posting in non-bugs section (such as this), use [Bugs], [Discussion] or [Suggestion] prefix in your thread name.

In case you object some action by a moderator, please contact him directly through PM and explain your concerns politely. If you are still unable to resolve the issue, contact an administrator. Do not drag these issues in public.

All rules are meant to augment common sense, please use them when not conflicted with aforementioned policies.
See more
See less

Python Dota 2 API Wrapper

  • Filter
  • Time
  • Show
Clear All
new posts

  • Python Dota 2 API Wrapper

    So, I've been using the WebAPI for mining games and realized that the response format was severely inconsistent across all the endpoints.
    I made a Python3 wrapper for it, with a rather nitpicky parser and I've attempted to unify the response results across all the endpoints to make its usage as uniform as possible.

    Link to source:

    As of now, I've dealt with fairly obvious inconsistencies such as and, as well as fixing inconsistent naming. I've also added a few QOL functions to relieve the user from manually parsing some stuff.

    One of the more aggravating problem that I had to fix, was that the WebAPI returned json data with repeating keys (see: The repeating "abilities" key is something inbuilt json parsers miss.

    I feel like the documentation is fairly decent (although it could be more contributor friendly) and was hoping to get feedback/criticism on it.

  • #2
    Thanks for making a Python Wrapper! I was also looking to create one, cant criticize yours since I dont have a lot of experience on doing this kind of things (binds/wrappers). So I will do my own first while learning things and then I might get back to you to give you so I can compare both

    Good work! #LongLivePython