Re: [SQLObject] Preventing Duplicate Class Definitions

[Brad B. <br...@bb...>]

On Friday, October 1, 2004, at 07:50  PM, Luke Opperman wrote:

> I'll see if I can get a unit test together to illustrate a problem 
> I've been
> having, but here's the scenario (may be a python import issue that we 
> can't
> get around either, I recall problems with imports with different 
> import lines,
> but here the lines at least look the same...)

[snip]

> but this leads to a duplicate class error from SQLObject.
>
> The full import pattern looks like:
>
> ./Page.py -> from Objects.User import User
> ./Objects.User is imported
> ./Page.py -> from Objects.Core.CheckUser import CheckUser
> ./Objects/Core/CheckUser.py -> from Objects.User import User
>
> Note, this is on an existing app using 0.5, I'll try to get some time 
> to track
> it down further next week.

It sounds like there's more to the problem you're experiencing than 
this, as Python wouldn't import the module twice in the scenario you're 
describing. I think good would be to come up with a small snippet of 
code to illustrate the problem you're experiencing, better would be to 
come up with a failing unit test and best would be to commit the code 
that passes the test. ;)

Cheers,

--
Brad Bollenbach