Difference between io.FileIO and open() in binary mode
They produce the same result based on checksum:
with open('openb', 'wb') as f:
f.write(b'asdf')
with io.FileIO('fileio', 'w') as f:
f.write(b'asdf')
Is there any difference between them? When should one method be used instead of the other?
python-3.x file-io
add a comment |
They produce the same result based on checksum:
with open('openb', 'wb') as f:
f.write(b'asdf')
with io.FileIO('fileio', 'w') as f:
f.write(b'asdf')
Is there any difference between them? When should one method be used instead of the other?
python-3.x file-io
add a comment |
They produce the same result based on checksum:
with open('openb', 'wb') as f:
f.write(b'asdf')
with io.FileIO('fileio', 'w') as f:
f.write(b'asdf')
Is there any difference between them? When should one method be used instead of the other?
python-3.x file-io
They produce the same result based on checksum:
with open('openb', 'wb') as f:
f.write(b'asdf')
with io.FileIO('fileio', 'w') as f:
f.write(b'asdf')
Is there any difference between them? When should one method be used instead of the other?
python-3.x file-io
python-3.x file-io
asked Nov 22 '18 at 13:49
dtgqdtgq
1,22421640
1,22421640
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Actually the open()
method will create an io.BufferedWriter
which inherits from IOBase
and FileIO
also inherits from IOBase
. Though not exactly the same classes, they support basically identical functionality. I suppose you could use FileIO if you know you don't need buffering. There's a lot of info on the python io docs page
The most important sentence there is:
Raw binary I/O typically provides low-level access to an underlying OS device or API, and does not try to encapsulate it in high-level primitives (this is left to Buffered I/O and Text I/O, described later in this page).
Raw binary I/O relates to io.FileIO and Buffered I/O to the io.BufferedWriter (open()
method)
So would it be correct to say thatopen()
is optimized for calling.write()
multiple times, but it is the same asio.FileIO
if only calling.write()
once?
– dtgq
Nov 22 '18 at 14:39
Honestly I haven't thought of that, but I think it is indeed correct to assume that.
– Borisu
Nov 22 '18 at 14:50
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432442%2fdifference-between-io-fileio-and-open-in-binary-mode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Actually the open()
method will create an io.BufferedWriter
which inherits from IOBase
and FileIO
also inherits from IOBase
. Though not exactly the same classes, they support basically identical functionality. I suppose you could use FileIO if you know you don't need buffering. There's a lot of info on the python io docs page
The most important sentence there is:
Raw binary I/O typically provides low-level access to an underlying OS device or API, and does not try to encapsulate it in high-level primitives (this is left to Buffered I/O and Text I/O, described later in this page).
Raw binary I/O relates to io.FileIO and Buffered I/O to the io.BufferedWriter (open()
method)
So would it be correct to say thatopen()
is optimized for calling.write()
multiple times, but it is the same asio.FileIO
if only calling.write()
once?
– dtgq
Nov 22 '18 at 14:39
Honestly I haven't thought of that, but I think it is indeed correct to assume that.
– Borisu
Nov 22 '18 at 14:50
add a comment |
Actually the open()
method will create an io.BufferedWriter
which inherits from IOBase
and FileIO
also inherits from IOBase
. Though not exactly the same classes, they support basically identical functionality. I suppose you could use FileIO if you know you don't need buffering. There's a lot of info on the python io docs page
The most important sentence there is:
Raw binary I/O typically provides low-level access to an underlying OS device or API, and does not try to encapsulate it in high-level primitives (this is left to Buffered I/O and Text I/O, described later in this page).
Raw binary I/O relates to io.FileIO and Buffered I/O to the io.BufferedWriter (open()
method)
So would it be correct to say thatopen()
is optimized for calling.write()
multiple times, but it is the same asio.FileIO
if only calling.write()
once?
– dtgq
Nov 22 '18 at 14:39
Honestly I haven't thought of that, but I think it is indeed correct to assume that.
– Borisu
Nov 22 '18 at 14:50
add a comment |
Actually the open()
method will create an io.BufferedWriter
which inherits from IOBase
and FileIO
also inherits from IOBase
. Though not exactly the same classes, they support basically identical functionality. I suppose you could use FileIO if you know you don't need buffering. There's a lot of info on the python io docs page
The most important sentence there is:
Raw binary I/O typically provides low-level access to an underlying OS device or API, and does not try to encapsulate it in high-level primitives (this is left to Buffered I/O and Text I/O, described later in this page).
Raw binary I/O relates to io.FileIO and Buffered I/O to the io.BufferedWriter (open()
method)
Actually the open()
method will create an io.BufferedWriter
which inherits from IOBase
and FileIO
also inherits from IOBase
. Though not exactly the same classes, they support basically identical functionality. I suppose you could use FileIO if you know you don't need buffering. There's a lot of info on the python io docs page
The most important sentence there is:
Raw binary I/O typically provides low-level access to an underlying OS device or API, and does not try to encapsulate it in high-level primitives (this is left to Buffered I/O and Text I/O, described later in this page).
Raw binary I/O relates to io.FileIO and Buffered I/O to the io.BufferedWriter (open()
method)
edited Nov 22 '18 at 14:36
answered Nov 22 '18 at 14:26
BorisuBorisu
42528
42528
So would it be correct to say thatopen()
is optimized for calling.write()
multiple times, but it is the same asio.FileIO
if only calling.write()
once?
– dtgq
Nov 22 '18 at 14:39
Honestly I haven't thought of that, but I think it is indeed correct to assume that.
– Borisu
Nov 22 '18 at 14:50
add a comment |
So would it be correct to say thatopen()
is optimized for calling.write()
multiple times, but it is the same asio.FileIO
if only calling.write()
once?
– dtgq
Nov 22 '18 at 14:39
Honestly I haven't thought of that, but I think it is indeed correct to assume that.
– Borisu
Nov 22 '18 at 14:50
So would it be correct to say that
open()
is optimized for calling .write()
multiple times, but it is the same as io.FileIO
if only calling .write()
once?– dtgq
Nov 22 '18 at 14:39
So would it be correct to say that
open()
is optimized for calling .write()
multiple times, but it is the same as io.FileIO
if only calling .write()
once?– dtgq
Nov 22 '18 at 14:39
Honestly I haven't thought of that, but I think it is indeed correct to assume that.
– Borisu
Nov 22 '18 at 14:50
Honestly I haven't thought of that, but I think it is indeed correct to assume that.
– Borisu
Nov 22 '18 at 14:50
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432442%2fdifference-between-io-fileio-and-open-in-binary-mode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown