Allow option for logging to co-exist with existing loggers

[jhay317]

Currently in the init.py a reset is performed for all loggers that exist. This can cause issues when this is integrated into other applications where logging is utilized. Two options on how this can be resolved are either an addition to the configuration file to allow_other_loggers: True or to expose the logger that exists within the PeeringDB API to be added to existing loggers. This is pretty common with other libraries.

[grizz]

Good point, thanks!

@peeringdb/pc This should get a priority for release.

[martinhannigan]

+1

…

On Fri, Oct 14, 2022 at 10:10 Matt Griswold ***@***.***> wrote: Good point, thanks! @peeringdb/pc <https://github.com/orgs/peeringdb/teams/pc> This should get a priority for release. — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFA2YQXCKWPT2JLJ6F7WGW3WDFSUFANCNFSM55MOE5OQ> . You are receiving this because you are on a team that was mentioned.Message ID: ***@***.***>

[floatingstatic]

Just ran into this. +1 for fixing