Module Name Problem

[Stephen Hansen]

This doesn't sound very broken,.. you're creating the conflict-of-names.. :)

I read somewhere the sugguestion of an 'import name as name' syntax..don't
know where...don't know if its a 1.6 or a py3k thing...

--S


Jerome Chan <eviltofu at rocketmail.com> wrote in message
news:eviltofu-E613EC.21014728062000 at news.earthlink.net...
> In article <8F61CAE59gmcmhypernetcom at 199.171.54.194>, gmcm at hypernet.com
> (Gordon McMillan) wrote:
>
> > Jerome Chan wrote:
> >
> > >If I have a module called
> > >
> > >maxvu.os
> > >
> > >and I use
> > >
> > >import os
> > >
> > >Somehow, when I try to use the os calls or maxvu.os calls it gets
> > >confused. Is there a workaround besides renaming my module?
> >
> >
> > Not if you want access to os within maxvu.
> >
> > - Gordon
>
> Will this be fixed in 1.6?