This looks like premature optimization to me. Write the code for maximum readability in the first instance. If it's too slow, benchmark then apply focused and documented changes to improve speed at bottlenecks.

print implies I/O which almost always implies unavoidable overhead that makes quite a lot of related "code inefficiency" irrelevant.