Package: pychallonge
pychallongePychallonge provides python bindings for theCHALLONGE!API.
The pychallonge module was created byRuss AmospychalPychal was a fork of pychallonge. The pychal module has been merged into
the pychallonge. If you are still using pychal you have to migrate to
pychallonge because it is not longer maintainedRequirementsiso8601tzlocalpytzrequestsPython version support2.73.4+InstallationFor the stable versionpip install pychallongeFor latest developmentpip install -e git+http://github.com/ZEDGR/pychallonge#egg=pychallongeUsageimportchallonge# Tell pychallonge about your [CHALLONGE! API credentials](http://api.challonge.com/v1).challonge.set_credentials("your_challonge_username","your_api_key")# Retrieve a tournament by its id (or its url).tournament=challonge.tournaments.show(3272)# Tournaments, matches, and participants are all represented as normal Python dicts.print(tournament["id"])# 3272print(tournament["name"])# My Awesome Tournamentprint(tournament["started_at"])# None# Retrieve the participants for a given tournament.participants=challonge.participants.index(tournament["id"])print(len(participants))# 13# Start the tournament and retrieve the updated information to see the effects# of the change.challonge.tournaments.start(tournament["id"])tournament=challonge.tournaments.show(tournament["id"])print(tournament["started_at"])# 2011-07-31 16:16:02-04:00Seechallonge.comfor full API
documentation.API IssuesThe Challonge API has some issues with the attachments endpoints. Thecreateandupdateendpoints are not working correctly. When you try
to upload an attachment with asset(file) the API returns 500 internal
server error. The same happens with asset + description. This issue
has been reported to Challonge.Another issue is the check in process has strange behaviour.
When you undo check in a participant the field 'checked_in' remains True
but in the website the participant is correctly not checked in.
That's why the module does not have any tests on this.Fixed by pychallonge: In the datetime fields the api returns random
timezone offsets, pychallonge convert those to your machine's local
time. Also you can set any timezone you want withset_timezonefunction.Running the unit testsPychallonge 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, setCHALLONGE_USERandCHALLONGE_KEYappropriately in your environment.$ git clone http://github.com/ZEDGR/pychalllonge pychallonge
$ CHALLONGE_USER=my_user CHALLONGE_KEY=my_api_key python pychal/tests.py
...............................
----------------------------------------------------------------------
Ran 31 tests in 98.176s

OKNote 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.importchallongechallonge.set_credentials("my_user","my_api_key")fortinchallonge.tournaments.index():ift["name"].startswith("pychal"):challonge.tournaments.destroy(t["id"])