On 8 Jan, 2006, at 7:32 pm, Michele Cella wrote:
Why the error with SQLite2?
On ubuntu (where pysqlite uses sqlite2) at least *everyone* that tries
tg will get this error, he should ask why, he should install a new
package, find it (it's named python-pysqlite2) and try again.
That's not a good first impression IMHO.
I don't know what's causing the error. I'm using SQLObject as per the
documentation. Perhaps there's a bug in the SQLObject code with
regard to SQLite2 (although someone indicated some MySQL users were
seeing the same problem).
Now that visit is in you can't start your project if you don't make a
db, I think that's really annoying (1 more step). It seems that this
happens even after disabling it (but I'm sure that I'm probably doing
something wrong).
That seems weird. Naturally, if you have Visit tracking enabled and
you don't have a DB that's going to cause trouble, but if Visit
tracking is disabled, it shouldn't complain...
Ah. Found it. I create the table in the constructor for the
VisitFilter, which is before I check whether Visit Tracking is
enabled... I should fix that or trap the exception...
The log is full of
...
2006-01-09 01:21:29,265 turbogears.visit DEBUG sending updates...
Removed. That was more for my testing purposes (I'd not used threads
with Python yet).
Again I think we shouldn't put identity on a quickstarted project.
At first sight less is better and easy to learn, at least in my
opinion.
Moreover identity is not required by every user and when you
quickstart
a project if you never used TG you start wondering what it's happening
inside login and logout with this big dict and cherrypy internals
exposed.
I disagree (obviously). Per a recent thread, adding support for
features after quickstart is problematic and basically too hard to do
right. So having all the goodies there is important.
On the otherhand, I agree that there's a lot of exposed nastiness
that can be improved. I was thinking of adding a controller to handle
login and logout which would hide most of the pipes and wires
currently exposed.
You should use
raise turbogears.redirect("/")
or
turbogears.redirect("/")
Cool. I remember seeing this bandied about, but didn't realise it was
in yet.
Anyway keep up the great work. ;-)
Actually, one of the features I *CAN'T* add to TurboGears is
aggregated identity from multiple sources (DB, LDAP, IMAP, etc)
because it would be considered a Single Sign On solution and my
employer (an SSO provider) would own it. Not good.
--
Jeff Watkins
http://newburyportion.com/
"Computers are like Old Testament gods; lots of rules and no mercy."
-- Joseph Campbell
