> You can only try and search the sys-path for the logging-module, using
>
> sys.prefix
>
> and then look for logging.py. Using
>
> __import__(path)
>
> you get a reference to that module.
>
> Diez
Thank you Diez, that's the info i'd been looking for :-)
So the answer is sys module + __import__
En Fri, 07 Mar 2008 12:15:04 -0200, koara <[EMAIL PROTECTED]> escribi�:
> On Mar 5, 1:39 pm, gigs <[EMAIL PROTECTED]> wrote:
>> koara wrote:
>> > Hello, is there a way to access a module that is hidden because
>> > another module (of the same name) is found first?
>>
>> > More specifically, i have
koara schrieb:
> On Mar 5, 1:39 pm, gigs <[EMAIL PROTECTED]> wrote:
>> koara wrote:
>>> Hello, is there a way to access a module that is hidden because
>>> another module (of the same name) is found first?
>>> More specifically, i have my own logging.py module, and inside this
>>> module, depending
2008/3/7, koara <[EMAIL PROTECTED]>:
>
> On Mar 5, 1:39 pm, gigs <[EMAIL PROTECTED]> wrote:
> > koara wrote:
> > > Hello, is there a way to access a module that is hidden because
> > > another module (of the same name) is found first?
> >
> > > More specifically, i have my own logging.py module, an
On Mar 5, 1:39 pm, gigs <[EMAIL PROTECTED]> wrote:
> koara wrote:
> > Hello, is there a way to access a module that is hidden because
> > another module (of the same name) is found first?
>
> > More specifically, i have my own logging.py module, and inside this
> > module, depending on how initiali
koara wrote:
> Hello, is there a way to access a module that is hidden because
> another module (of the same name) is found first?
>
> More specifically, i have my own logging.py module, and inside this
> module, depending on how initialization goes, i may want to do 'from
> logging import *' fro
