Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #12865
| Date | 2011-09-07 11:11 +1000 |
|---|---|
| From | Mark Hammond <skippy.hammond@gmail.com> |
| Subject | Re: import os or import os.path |
| References | <CAOuJsM=vZL1kLgNkgpD6fC=J3APHJTN2RKLGySD9-p0JnxcpzQ@mail.gmail.com> <CALwzidnhfOPVPPzBqpc8P6WqwEE=QFmRufrnxf=vA2tnbThAJA@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.815.1315358357.27778.python-list@python.org> (permalink) |
On 7/09/2011 7:47 AM, Ian Kelly wrote:
> On Tue, Sep 6, 2011 at 3:25 PM, Jabba Laci<jabba.laci@gmail.com> wrote:
>> Hi,
>>
>> If I want to use the 'os.path' module, it's enought to import 'os':
>>
>> import os
>> if os.path.isfile('/usr/bin/bash'):
>> print 'got it'
>>
>> In other source codes I noticed that people write 'import os.path' in
>> this case. Which is better practice?
>
> "import os.path" is better practice. There is no guarantee in general
> that the os module will automatically import os.path, and in future
> versions or different implementations it might not.
That's probably a matter of opinion - eg,
http://docs.python.org/tutorial/interpreter.html has an example of
importing the os module then accessing os.path.
Personally I think directly importing os.path is a waste of precious
keystrokes ;)
Cheers,
Mark.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: import os or import os.path Mark Hammond <skippy.hammond@gmail.com> - 2011-09-07 11:11 +1000
csiph-web