Difference between io.FileIO and open() in binary mode












0















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?










share|improve this question



























    0















    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?










    share|improve this question

























      0












      0








      0








      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?










      share|improve this question














      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 22 '18 at 13:49









      dtgqdtgq

      1,22421640




      1,22421640
























          1 Answer
          1






          active

          oldest

          votes


















          1














          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)






          share|improve this answer


























          • 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











          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
          });


          }
          });














          draft saved

          draft discarded


















          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









          1














          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)






          share|improve this answer


























          • 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
















          1














          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)






          share|improve this answer


























          • 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














          1












          1








          1







          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)






          share|improve this answer















          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)







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 22 '18 at 14:36

























          answered Nov 22 '18 at 14:26









          BorisuBorisu

          42528




          42528













          • 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



















          • 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

















          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


















          draft saved

          draft discarded




















































          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.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          Create new schema in PostgreSQL using DBeaver

          Deepest pit of an array with Javascript: test on Codility

          Costa Masnaga