import os
Dan Stromberg
drsalists at gmail.com
Sun Nov 16 20:15:33 EST 2014
More information about the Python-list mailing list
Sun Nov 16 20:15:33 EST 2014
- Previous message (by thread): import os
- Next message (by thread): import os
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Nov 16, 2014 at 5:10 PM, Abdul Abdul <abdul.sw84 at gmail.com> wrote: > Thanks for your reply. Yes, I came across this page, but didn't understand > what is meant by the operating system dependent functionality. What does > that mean? Is importing that module that serious? The os module has mostly lower level OS interfaces; there are sometimes higher level equivalents elsewhere in the language. It's not bad to use os, but for EG, file operations os.open/os.read/os.write/os.close, it's better to use "with open as file_", file_.read, file_.write. Another example is os.fork() - you can use it, but you're probably better off with the subprocess module or the multiprocessing module. You don't really have to worry about breaking anything by using the os module - at least, not particularly more than the higher level interfaces for the same thing.
- Previous message (by thread): import os
- Next message (by thread): import os
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list