Re: import os or import os.path

From	Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject	Re: import os or import os.path
Date	2011-09-06 23:35 -0700
Organization	> Bestiaria Support Staff <
References	<CAOuJsM=vZL1kLgNkgpD6fC=J3APHJTN2RKLGySD9-p0JnxcpzQ@mail.gmail.com> <CALwzidnhfOPVPPzBqpc8P6WqwEE=QFmRufrnxf=vA2tnbThAJA@mail.gmail.com> <4E66C4DB.7080008@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.821.1315377359.27778.python-list@python.org> (permalink)

Show all headers | View raw

On Wed, 07 Sep 2011 11:11:55 +1000, Mark Hammond
<skippy.hammond@gmail.com> declaimed the following in
gmane.comp.python.general:

> 
> 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 ;)
>
	Ah, but 

import os.path as op

supports a lot of later keystroke saving...

	op.join(...)
vs
	os.path.join(...)
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
        wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: import os or import os.path Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2011-09-06 23:35 -0700

csiph-web