Share this project using http://git.io/todo.py and this page using http://git.io/todo.py-wiki.

Example usage of commands can be found on the help page. Sample configuration files can be found on the config page. Explanations of configuration options can be found here.

We have tried to almost entirely mimic todo.sh's behavior. It'll just be easier to list the differences.

• If the todo.txt file is empty, todo.py will ignore it until it has to add something to the file.¹
• If you so desire, you do not need to have done.txt, report.txt, or todo.tmp files lying around your directories.²
• Previously you would tell todo.sh to archive your todo.txt file which would move all the entries you had marked as 'done' to the done.txt file. I (sigmavirus24) decided it was just simpler for a new user to understand that what they mark as done will appear in the done.txt file.
• Git integration is baked into the project from the start. This allows the script to manage a repository for your todo.txt files. This does not have to be used though. Simply use export USE_GIT=0 in your config file.
• Exporting a sort command will not work. (i.e. TODOTXT_SORT_COMMAND)

"todo.sh is 14x slower than this impl on Cygwin, so I'm replacing it. Need the same output, though." - jvstein

• Python 3
• Installing

If you would rather use python3 for your todo.py script, we support it! Just change the first line of the script from

#!/usr/bin/env python

to

#!/usr/bin/env python3

Assuming of course that you have python3 installed along with python2. If you only have python3 installed, you should not have to do this.

It is usually easier to simply install the script to a local directory like $HOME/bin so you can always make this executable from any directory by adding that path to your PATH variable, e.g. export PATH="$PATH:$HOME/bin".

1. https://github.com/sigmavirus24/Todo.txt-python/issues/11↩

2. https://github.com/sigmavirus24/Todo.txt-python/issues/10↩