kimes wrote:
> You said 'At first os - module, or package, it doesn't matter here - is
> imported.'
With a file mop.py in your path
import mop
creates a module instance and executes mop.py to fill it with content --
classes, functions, whatever python objects you can think of -- and puts
that m
On Sunday 17 July 2005 12:47 pm, kimes wrote:
> Thanks for all you guys help..
> I'm still confused about that..
> When I just call import os.path without calling import os..
> In that case, you mean 'import os' is called implicitly?
> Why? and How?
>
> how python knows it should call import when
Thanks for all you guys help..
But Peter,
You said 'At first os - module, or package, it doesn't matter here - is
imported.'
I'm still confused about that..
When I just call import os.path without calling import os..
In that case, you mean 'import os' is called implicitly?
Why? and How?
how pyt
look at 'path' module too
http://www.jorendorff.com/articles/python/path/
--
http://mail.python.org/mailman/listinfo/python-list
kimes wrote:
> But the only os.path doesn't have their own file..
> ye I know is has actually depending on os like in my case posixpath..
>
> What I'd love to know is..
> when I call import os.path..
> how happened under the hood?
At first os - module, or package, it doesn't matter here - is imp
kimes wrote:
> I've just started digging into how python works..
> I found that other mudules are clearly declared like one file per a
> module..
>
> But the only os.path doesn't have their own file..
> ye I know is has actually depending on os like in my case posixpath..
>
> What I'd love to kno
I've just started digging into how python works..
I found that other mudules are clearly declared like one file per a
module..
But the only os.path doesn't have their own file..
ye I know is has actually depending on os like in my case posixpath..
What I'd love to know is..
when I call import os.
