We should stop using non-public `scanpy.logging.info`

[selmanozleyen]

Description of feature

Continuation of #1076 (comment)

@ilan-gold scanpy.logging looks pretty public https://github.com/scverse/scanpy/blob/f3d270dbb996a88741f321e213527d2c0a1f8116/src/scanpy/__init__.py#L59 are you sure its not?

If not we should remove them. Also using spatialdata._logger doesn't sit well with me since this one looks like the private one lol. In this issue we should decide what to use.

[ilan-gold]

are you sure its not?

Just because the module looks public doesn't mean its contents are public. Check out the scanpy docs

These are the only two things we have publicly available. Docs are our source of public truth: https://scanpy.readthedocs.io/en/stable/api/index.html

[selmanozleyen]

Just because the module looks public doesn't mean its contents are public. Check out the scanpy docs

yeah sure but I wouldn't blame anyone who uses this. Sounds like it could be a common pitfall. Because in many packages logger comes with a logging. The contents look more like they would belong to options, version or settings tbh

[ilan-gold]

We have a note about this on the anndata homepage but it applies to scanpy as well: https://anndata.readthedocs.io/en/stable/#public-api

I will add it

[selmanozleyen]

That's fair but I just don't get why not making f.e.:_logging_utils.py and logging.py (if we want to keep the public logging) in this case.