Replace prints with logging

[pollytur]

After replacing print with logging - we would need to check that this did not influenced the efficiency of the code (benchmark with multiple data loader threads? think if we want to log from 1 worker only or if we want to set sth like logger.propagate = False)

[Vrittigyl]

Hi, I'd like to work on this.

I'll replace the print calls with logging.getLogger(__name__). For multi-worker DataLoader cases, I'll ensure logging is configured properly to avoid duplicate handlers, and benchmark to check for any performance impact (including whether logger.propagate = False is needed).

[pollytur]

@Vrittigyl for profiling - you might look at #97

[passionworkeer]

A low-risk way to do this is to replace print with module-level loggers but keep message construction lazy (logger.debug("... %s", value)) so disabled levels stay cheap. For multi-worker DataLoader runs, I��d avoid adding handlers in library code and let the application configure handlers once; otherwise duplicate lines usually come from repeated handler setup, not propagation alone. Benchmarking with logging disabled vs enabled at INFO/DEBUG and with multiple workers should make the regression surface pretty clear.