There are only few parts where print() is used to communicate what's happening within the library as compared to log.info(). I suggest to enable logger with INFO defaults instead of DEBUG, so in that way the library can uniformly communicate throughout the logger.
When application is not started yet, the socket host and port can change from default. Then, instead of forcing this to default, let's allow developer to choose at which socket host and port is the application listening, otherwise, let's propagate the defaults values coming __init__(). Does this make sense to you?
Let me know your thoughts. I already bumped to upcoming version as well.
I would like contribute with the following:
print()
is used to communicate what's happening within the library as compared tolog.info()
. I suggest to enable logger withINFO
defaults instead ofDEBUG
, so in that way the library can uniformly communicate throughout the logger.__init__()
. Does this make sense to you?Let me know your thoughts. I already bumped to upcoming version as well.