Well, it appears that people are using twill -- I got a few testy comments along the lines of, "why does twill 0.8.2. not work AT ALL"? So I fixed that (I ended up just including BeautifulSoup with twill) and released twill 0.8.3.
Back When, I mentioned SvnReporter, a reporting program for subversion repositories. I just installed it and I'm happy to report that the mailing component works. I haven't tried the RSS feed component out -- I don't really have a need for it, although if Grig asks me to I'll add it -- but it's nice to receive informative e-mails on each commit.
My only comment is that it seems a bit over-engineered for my needs, but my needs are fairly simple and I didn't devote a lot of time to grokking the documentation, either. I just hacked and slashed the example file until it stopped complaining and e-mails started coming ;).
Installing the thing was a real bitch, though, through no real fault of Remy Blank's (the author). For reasons of decorators (and maybe more), SvnReporter requires Python 2.4. That's well and good, but it also requires subversion bindings. Unfortunately (for this purpose) I'm using Debian, and python2.4-subversion doesn't exist except in Ubuntu. I tried to compile the subversion Python bindings (...which requires the entire subversion source tree), but that failed for no good reason, twice. After the first monkeypatch for the APR_PATH_MAX problem succeeded, I hit a link problem. I quickly lost interest in going this route.
In the end I just sym-linked the Python 2.3 bindings into the Python 2.4 site-packages directory. Ugly and fragile, but it works.
One lesson that I'd like to repeat: if you want people to use your Python software, write it for Python 2.3. This would have been a 5 second install for me, rather than a 2 hr trek that I nearly abandoned.
I'd like to echo grig on using setuptools, with perhaps a tad more specifics:
MAKE YOUR PACKAGE INSTALLABLE WITH EASY_INSTALL.
This amounts to:
- writing a distutils-compatible setup.py.
- publishing your package on PyPi.
Note how neither of these requires doing anything setuptools-specific? Yep.
If you feel like using setuptools.require and some of the other setuptools "magic", then you might be limiting your audience. But publishing a Python package via PyPi with a setup.py script is sufficient to make it easy_install-able.
Now, while we're griping about setuptools: yes, the --help stuff is silly and confusing. It would also be very, very nice to be able to say 'setuptools.require("Python>=2.3"), which currently doesn't work.