`Logging` support

[ndem0]

[adendek]

I'd be happy to take this on. Could you confirm if this task is suitable for an open-source contributor?

Regarding the logging implementation, what level of sophistication are you aiming for in the configuration?

I suggest considering Loguru. It provides aesthetically pleasing logs out-of-the-box with minimal configuration. However, it defaults to redirecting all logs to stderr, and I'd like to confirm if this behavior is acceptable.

Alternatively, for a more robust solution, we could utilize structlog. While it requires more effort in initial configuration, it offers significantly greater flexibility and control.

Please let me know your preference between these options. I'm prepared to set up the chosen logger and implement initial logging in the main classes.

[dario-coscia]

Hi @adendek! Thanks for the interest!

Yes this is suitable for an open source contributor, it might take some time and we should agree on a common pipeline for the implementation (we can do everything here).

I would go for structlog has it will allow more flexibility in the future.

I would add logging in a first instance to.

-> Trainer
-> Abstract Problem
-> Solver interface
-> Dataloader

For all of these we should clearly state what we want to log for DEBUG, INFO (at least the start).

Let's try to set a tentative schedule for this? Maybe the easy way to start is (i) to have a general roadmap of things which will be implemented, and (ii) to create a file logging.py in pina/ with some utilities function

[adendek]

Apology for the late response. @dario-coscia when do you plan to start working on that? Can this be addressed next week? I'll definitly find some time to work on this.

[dario-coscia]

Hi @adendek, we haven't set a deadline for it yet. Eventually, we will feature this in the 0.3 version, which we plan to release in June. If you plan to work on it next week, it is totally fine, we can also think to add it to the already 0.2 if ready before June.

To start, just open a Draft PR with a general roadmap of things that will be implemented, and create a file logging.py in pina/ with some utility functions (or empty at the beginning)