Logging
rmnldwg opened this issue · comments
Implement some logging for more feedback while using the package.
Not sure this makes a lot of sense, since the package can't be executed on its own. One always has to write code using this library, so logging can - and probably should - be implemented at that point.
It does make sense and I implemented a basic logging setup and some first logging statements here and there.
For example, the __init__.py
of my package now has a minimal logging setup inspired by urllib3's logging setup. This way, anyone who is using my library within some other framework or tool may simply turn on the lymph
package's logging via the provided function.