ballcosmos destroys logging configuration

[keck-in-space]

if ballcosmos is imported it overwrites my existing logging configuration

[keck-in-space]

python-ballcosmos/ballcosmos/__init__.py

Lines 21 to 24 in 86ec6d2

	logging.basicConfig(
	format="%(asctime)s %(levelname)s %(name)s %(message)s",
	level=logging.getLevelName(LOG_LEVEL),
	)

If I comment out these lines I don't get the logging behavior overwrite

[AbdelAzizMohamedMousa]

The logging.basicConfig() function is used to configure the logging system in Python. It should be called only once at the beginning of the program to set up the logging configuration.

By calling logging.basicConfig() more than once, the configuration of the logging system will be reset to its default settings, and any previous logging configuration will be lost.

In the code you provided, calling ballcosmos() after logging.basicConfig() will reset the logging configuration to its default settings and destroy any previous logging handlers, which may cause unexpected behavior in the logging system.

If you need to use ballcosmos() after configuring the logging system, you should ensure that it does not reset the logging configuration, or you should reconfigure the logging system after calling ballcosmos().

[keck-in-space]

I understand that, but a Python library should not be setting the logging configuration.