pydidit Git
Status: Pre-Alpha
Brought to you by:
adamlincoln
pydidit ====== Adam J. Lincoln <adamjlincoln@gmail.com> (Primary author and current maintainer) pydidit is a todo system designed to be flexible enough to fit your style. HISTORY ======= The original author used and liked tracks 1.7 (http://getontracks.org), and wanted some more features. He didn't know ruby and eventually decided that a conceptual overhaul was in order, so he wrote his own todo system from scratch. USE === Originally developed with Python 2.6, sqlalchemy 0.4.8, postgres 8.3.7, and psycopg2 2.0.8. Probably works with other combinations, but isn't tested. You'll need to install sqlalchemy 0.4.8 and a python postgres DB API (I use psycopg2 2.0.8, but I think anything that sqlalchemy supports is good). On debian-based distros, you can probably just 'apt-get install python-sqlalchemy python-psycopg2' and be ready to go. To use the gtk frontend (still under development), you'll also need the pygtk bindings. The command line switch -f or --frontend selects the curses or gtk frontend. Do './pydidit --help' for more info. I've provided a bash script, setup_database.sh, that may help you get your pydidit database set up. Read the comments at the top of it before running it, please. You'll also need to make a .pydiditrc file in your home directory. A sample-pydiditrc has been provided. Note that if you didn't do anything special for authenticating to postgres, then you don't need to do anything to the .pydiditrc file. It would still be a good idea to copy the sample-pydiditrc to ~/.pydiditrc, as later there may be settings there you'll want to play with. Aside from the database and config file, you should be able to put all pydidit source files in a directory, verify that pydidit has execute permissions, and run it directly. MISCELLANEOUS ============= More info coming as things develop. No manpage yet. Some interactive help is available by pressing 'h' in pydidit. This is early alpha software, and while the GPLv3 makes it clear there is no warranty, I want to emphasize that very little error checking is done, and I can't promise some strange condition will not blow away your todo lists. Patches are always welcome, and will be accepted if the maintainer thinks it's a good idea, which is generally not a high threshold. Until some kind of infrastructure is set up, please send patches to the current maintainer (listed at the top of this file and in the AUTHORS file). Questions/suggestions/comments are also highly encouraged.