Alberto wrote:
Reloader thread?? Do you mean:
a) the template reloader? (I'm too lazy/busy to check right now in the
code if it's threaded or something.
b) the visit-expiration-time-updater-thread?
c) cherrypy's module reloader?
d) none of the above.
I meant a & c. You can't turn off the visit updater thread. (If someone
doesn't want it, he can turn off Visit Tracking all together.)
If the answer is (a), the yes as I'm running with kid.precompiled=True
as to work around the "None not callable" bug on a semi-production
site.
If you mean (c) then yes as it's on "production" environment (I think
cherrypy's autoreloader thread is off in "production", am I wrong?).
Grrr... I was afraid of that. I'll look at the code to see whether
there's anything else I can do to make certain this doesn't come up.
Part of the problem is that the Visit code *may* be executing outside
the standard TG transaction. I try to wrap the operations in a
transaction to get around SQLObject's broken caching, but I guess it
didn't work.
I'm pretty sure it's not an identity bug anyway, just what made the bug
arise so this probably shouldn't have spilled to your side. It's the
first thing I saw on the traceback though, and I posted way before
investigating... my apologies.
Hah. I wasn't really worried it was a visit/identity bug (it just didn't
feel like it), but I don't want anything to stand in the way of TG
developers *using* visit/identity.
--
Jeff Watkins
http://newburyportion.com/
