Make logging in core user controlled

[rozyczko]

Core logs a lot of warnings to STDOUT. Those should be user controllable.
If a technique-specific library doesn't want the core to pollute standard output, there should be a way to switch those logging messages off.

[rozyczko]

Interestingly, warnings like warnings.warn(DeprecationWarning) can't be easily screened out. Those warnings are issued from a different module than the top-level package name (easyscience).
We should replace warnings.warn with proper logging, unforunately.

[damskii9992]

Interestingly, warnings like warnings.warn(DeprecationWarning) can't be easily screened out. Those warnings are issued from a different module than the top-level package name (easyscience).
We should replace warnings.warn with proper logging, unforunately.

Doesn't this do what you want?
https://stackoverflow.com/questions/3920502/how-to-suppress-a-third-party-warning-using-warnings-filterwarnings

[rozyczko]

But then, you're effectively stopping warnings from your module as well. We only want a way to stop STDOUT from core.

Also,

>>> warnings.filterwarnings("ignore", category=DeprecationWarning, module=r"easyscience")
>>> a = ObjBase(name="1")
<stdin>:1: DeprecationWarning: ObjBase is deprecated and will be removed in a future version. Please migrate to ModelBase

still visible.