[Python-Dev] unexpected import behaviour

P.J. Eby pje at telecommunity.com
Fri Jul 30 23:03:20 CEST 2010


At 11:50 PM 7/30/2010 +0400, Oleg Broytman wrote:
>On Fri, Jul 30, 2010 at 07:46:44PM +0100, Daniel Waterworth wrote:
> > can anyone think of a case where someone has
> > been annoyed that, having imported that same module twice via
> > symlinks, they have had problems relating to modules being independent
> > instances?
>
>    I've had problems with two instances of the same module imported after
>sys.path manipulations. Never had a problem with reimported scripts.

I have.  The "unittest" module used to have this problem, when used 
as a script.



More information about the Python-Dev mailing list