Patrick, This is a known problem. See here:
http://trac.turbogears.org/turbogears/ticket/76 The identity code still needs a lot of work before it is ready for the 0.9 release. Keep in mind that the code in SVN is under development - released versions will have less bugs, better docs, etc. Sean Cazzell On Tue, 2005-11-15 at 19:59 -0800, Patrick Lewis wrote: > I just got around to checking out the subversion trunk, and stumbled on > a name conflict. I had a sqlobject class named User in a project I'm > working on, and this conflicts with the new identity User. I don't > have identity turned on (looks like that is the default). Last line of > the traceback is: > > ValueError: class User is already in the registry (other class is > <class 'foo.model.User'>, from the module foo.model in > /Users/plewis/Programming/TurboGears/foo/foo/model.pyc; attempted new > class is <class 'turbogears.identity.model.somodel.User'>, from the > module turbogears.identity.model.somodel in > /Users/plewis/Programming/turbogears_svn/trunk/turbogears/identity/model/somodel.pyc) > > I guess the general question I have is should there be a specific > namespace of some type for turbogears objects (e.g. TGUser, TGGroup)? > Are there other turbogears models that are registered? If the answer > is User and Group are reserved for turbogears, I suppose that's fine, > but it should probably be documented as such. >
