Only supports python3.3+

python-anydo

Unofficial python bindings for Any.Do, an attractive todo list organizer.

The bindings cooperate with the official applications available viz:

Usage Guide

Authenticate to Any.Do and create AnyDoAPI object

from anydo.api import AnyDoAPI
api = AnyDoAPI(username='[email protected]', password='password')

Get User Information

api.get_user_info()

Get All Tasks (including Notes)

api.get_all_tasks()

Get Task/Note by ID

api.get_task_by_id()

Delete Task/Note by ID

api.delete_task_by_id()

Get All Categories

api.get_all_categories()

Delete Category by ID

api.delete_category_by_id()

Create new category

api.create_new_category()

Create new task

api.create_new_task()

Developing python-anydo

You should add bin/runtest.sh as pre-commit git-hook. It will help you in verifying your changes locally.

$ git clone https://github.com/dustinbrown/python-anydo.git
$ cd python-anydo
$ cp bin/runtest.sh .git/hooks/pre-commit

License

The MIT License (MIT)

Copyright (c) 2014 Gaurav Kalra

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Authors

• Gaurav Kalra ([email protected])
• Kouhei Maeda ([email protected])
• Dustin Brown ([email protected])