Thanks; I'm gonna have to comb through that code later and try to figure out
how to avoid this.
2011/5/10 Oleg Broytman <p...@phdru.name>
> On Tue, May 10, 2011 at 03:33:43PM -0600, Pгoм???тн?????s 0x01 wrote:
> > Is there something I can do to catch this? Should I be using some kind of
> > registry or dictionary to keep track of imports? (Would that help?)
>
> In my experience, problematic import is usually a result of mixed
> absolute and relative import - a submodule A imports submodule X as
> parent.X and submodule B imports X as X; add sys.path manipulations and
> voila - X is imported both as parent.X and top-level X.
>
> Oleg.
> --
> Oleg Broytman http://phdru.name/ p...@phdru.name
> Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> sqlobject-discuss mailing list
> sqlobject-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
