pychallonge

Pychallonge provides python bindings for the CHALLONGE! API.

Requirements

• iso8601
• aiohttp

Python version support

• 3.5

Installation

pip install -e git+http://github.com/fp12/pychallonge_async#egg=pychallonge_async

Usage

import asyncio
from challonge import Account

async def pychallonge_async()
    # Create an Account instance with your [CHALLONGE! API credentials](https://challonge.com/settings/developer).
    account = Account('your_challonge_username', 'your_api_key')

    # Retrieve a tournament by its id (or its url).
    tournament = await account.tournaments.show(3272)

    # Tournaments, matches, and participants are all represented as normal Python dicts.
    print(tournament['id']) # 3272
    print(tournament['name']) # My Awesome Tournament
    print(tournament['started-at']) # None

    # Retrieve the participants for a given tournament.
    participants = await account.participants.index(tournament['id'])
    print(len(participants)) # 13

    # Start the tournament and retrieve the updated information to see the effects of the change.
    tournament = await account.tournaments.start(tournament['id'])
    print(tournament['started-at']) # 2011-07-31 16:16:02-04:00

See challonge.com for full API documentation (XML results).

Running the unit tests

Pychallonge comes with a set of unit tests. The tests are not comprehensive, but do utilize each method and verify basic functionality.

In order to test behavior of the python bindings, API calls must be made to CHALLONGE!, which requires a username and api key. To run the tests with your credentials, set CHALLONGE_USER and CHALLONGE_KEY appropriately in your environment.

$ git clone http://github.com/fp12/pychallonge pychallonge
$ CHALLONGE_USER=my_user CHALLONGE_KEY=my_api_key python pychallonge/tests.py
....................
----------------------------------------------------------------------
Ran 21 tests in 15.022s

OK

Note that several tournaments are created, published, started, and completed over the course of the unit tests. These should be cleaned up by the end, but if any of the tests fail they may not be cleaned up. As long as the basic functions work, you can clean up errant tournaments as follows.

   import challonge
   account = Account('your_challonge_username', 'your_api_key')
   for t in account.tournaments.index():
       if t["name"].startswith("pychallonge"):
           await challonge.tournaments.destroy(t["id"])