On 4/18/11 3:31 PM, "Sam Hartman" <[log in to unmask]> wrote:
>Would it be reasonable for you to trash it, but re-import and replace
>that module property?
I think it's technically possible (I haven't checked, but I donšt think
modules have ownership of properties, the namespace is global). There's a
question of who should bear the cost of the problem, and if I'm the only
module with the problem, it wouldn't be wrong to put the cost there.
>If not, then yes, having a name only context would be a reasonable thing
>for him to do.
>I agree trashing the context you get from him is problematic and I now
>see the problem more clearly.
So, having not considered that multiple imports would be workable, that
would probably be my work-around if need be. It's less work than unpacking
and serializing it all myself.
-- Scott
|