Identity model problems while upgrading to TurboGears 1.0b2

2 views
Skip to first unread message

Christopher Arndt

unread,
Dec 12, 2006, 9:33:19 AM12/12/06
to turbo...@googlegroups.com
I ran into a strange problem, when I tried to upgrade TG to 1.0b2 today.

Here's a little writeup of the symptoms, diagnosis and cure:

http://paddyland.serveblog.net/article/14

Summmary:

If you get the following error after upgrading:

TypeError: VisitIdentity() did not get expected keyword argument user_id

then your model.py was probably generated with a TG version from before
changeset 1603 (http://trac.turbogears.org/turbogears/changeset/1603) and you
have to update the Visit class manually.

HTH, Chris

Jorge Vargas

unread,
Dec 12, 2006, 11:09:00 AM12/12/06
to turbo...@googlegroups.com
yes this was discuss on the mailing list and was supposed to appear on
the changeLog there is one thread on this mailing list and another on
the trunk too.

but you got to the same conclusion :)

> HTH, Chris
>
> >
>

Christopher Arndt

unread,
Dec 12, 2006, 11:17:30 AM12/12/06
to turbo...@googlegroups.com
Jorge Vargas schrieb:

> yes this was discuss on the mailing list and was supposed to appear on
> the changeLog there is one thread on this mailing list and another on
> the trunk too.

I searched Google and the mailing list for the error message and nothing turned
up. This should change now ;-)

Chris

Jorge Vargas

unread,
Dec 12, 2006, 12:46:49 PM12/12/06
to turbo...@googlegroups.com
On 12/12/06, Christopher Arndt <chris...@web.de> wrote:
>
> Jorge Vargas schrieb:
> > yes this was discuss on the mailing list and was supposed to appear on
> > the changeLog there is one thread on this mailing list and another on
> > the trunk too.
>
> I searched Google and the mailing list for the error message and nothing turned
> up.
the original thread is
http://groups.google.com/group/turbogears-trunk/browse_thread/thread/bee11787f03e9b1e

This should change now ;-)

yea indeed none of them had a good name yours does


>
> Chris
>
> >
>

Reply all
Reply to author
Forward
0 new messages