|
From: Brad B. <br...@bb...> - 2003-10-14 18:29:23
|
On Tuesday, October 14, 2003, at 02:21 PM, Ian Bicking wrote: > On Tuesday, October 14, 2003, at 01:17 PM, Brad Bollenbach wrote: >> On Tuesday, October 14, 2003, at 02:05 PM, Ian Bicking wrote: >> >>> First, are you using CVS? There's a bug in 0.4 related to this. >>> CVS will be 0.5 once I package it up. >> >> Yep, just updated SQLObject a moment ago right from SourceForge to be >> double-sure. > > Can you double-check the installation? I definitely remember this bug > showing up with this exact same sort of exception in the past. If > that doesn't help, I won't be able to look at this until tonight. Ugh, I had a custom (older, of course) version of SQLObject living in the same directory as the relevant module being imported, so even though the CVS version of SQLObject was in the first directory in my PYTHONPATH, it was never getting seen. Moved that version out of the way so that the CVS version gets seen, and it Does The Right Thing now. I could use a dark corner to crawl into right now. -- Brad Bollenbach BBnet.ca |
