On my day off, I’m at IndyHall hacking around on a python module for doing some Taskpaper tasks from the command line. I call my creation TaskPyper! Yes, that’s bad of a name. I know already, lets move on.
Part of doing this was to spend some time learning to package and get code distributed along the way. I expected that repository stuff would be hard, and installer/packaging would be easy. Instead I found it was the other way around.
Oddly enough getting a project up on google code was dirt easy. I’ve tried to work with sourceforge before, and had some luck, but it always was a 3 or 4 step process. Google code it took just a minute to fill out a form to get taskpyper setup in their repo. The only confusion I had at all was that my google code repository password is different from my general google password. Which makes a lot of sense, but wasted 5 min. of my life to figure out.
Repository in hand, I started to wrap my code into a module. Finding the best practices for making a small module was a bit frustrating. Python’s own Module page is a decent read, but a bit obtuse, and it doesn’t help much in deciding how or what to package. There is a Distributing Python Modules page, but that didn’t really scratch my itch either. I ended up just mashing the best advice from both and putting that into the repository. I’m still a little unsure, and unsatisfied with the solution I put together from those pieces.
Anyway, it’s nice to have spent 3 hours, and generated a small tool that solves one problem. In this case, listing todays tasks on the command line. It’s also nice to have a small hobby code project to work on where I can concentrate being driven to craft code, rather than be driven to Get Things Done for a release.