As per the docs

first do f.flush(), and then do os.fsync(f.fileno()), to ensure that all internal buffers associated with f are written to disk.

Here is an example,

import os

with open("filename", "w") as f:
    while True:  # infinite program
        f.write("the text")
        f.flush()
        os.fsync(f.fileno())

For writing the internal buffer to the file you can use the files flush function. However, this should generally be handled by your operating system which has a default buffer size. You can use something like this to open your file if you want to specify your own buffer size:

f = open('file.txt', 'w', buffering=bufsize)

Please also see the following question: How often does Python flush to file

Alternatively to flushing the buffer you could also try to use rolling files, i.e. open a new file if the size of your currently opened file exceeds a certain size. This is generally good practice if you intend to write a lot of data.

For file operations, Python uses the operating system's default buffering unless you configure it do otherwise. You can specify a buffer size, unbuffered, or line buffered.

For example, the open function takes a buffer size argument.

http://docs.python.org/library/functions.html#open

"The optional buffering argument specifies the file’s desired buffer size:"

• 0 means unbuffered,
• 1 means line buffered,
• any other positive value means use a buffer of (approximately) that size.
• A negative buffering means to use the system default, which is usually line buffered for tty devices and fully buffered for other files.
• If omitted, the system default is used.

code:

bufsize = 0
f = open('file.txt', 'w', buffering=bufsize)

Looks like it writes the output to some buffer

That's correct. You can disable this with flush=True, so:

while True:
  print('tick', flush=True)
  time.sleep(5)

doWrite isn't there for you to call. It is part of the interface between the transport and the reactor. It is not part of the interface between the transport and the protocol.

FileDescriptor does not buffer writes until a certain number of bytes have been written. It only buffers writes (at most) until the reactor gets a chance to run again. Twisted is a cooperative multi-tasking system. Only one thing happens at a time. If the one thing that's happening is your application code running then the reactor isn't taking care of its job (like writing bytes to file descriptors). Each thing has to wait for the other to finish before it can start.

Whatever led you to the conclusion that there's a size-based write buffer was a mistake. Whatever problem you're trying to solve, the solution doesn't look like this.

To actually answer the question if you really want to use BufferedWriter.

import io

buffer_size = <number of bytes>

# Open the file unbuffered because we don't want to buffer twice.
with open("myfile.bin", "wb+", 0) as raw_file:
  with io.BufferedWriter(raw_file, buffer_size) as buffered_file:
    buffered_file.write(b"<your data>")

This works for binary files, if you want to do this but with text you need TextIOWrapper.

import io

buffer_size = <number of bytes>

# Open the file unbuffered because we don't want to buffer twice.
with open("myfile.txt", "wb+", 0) as raw_file:
  with io.BufferedWriter(raw_file, buffer_size) as buffered_file:
    # Again, turn off buffering because we're handling that.
    with io.TextIOWrapper(buffered_file, write_through=True) as buffered_text_file:
      buffered_text_file.write("<your data>")

Nested with statements can be written like

with (
  context_manager1 as foo,
  context_manager2 as bar,
  ...
):
  ...

to avoid the deep nesting but if you don't know the shorthand it can look confusing.