bug: Deprecation Warning

[MaKaNu]

Description of the bug

I recognized today the following deprecation warning and since #173 is closed I guess Griffe is not in fault?

INFO    -  DeprecationWarning: Setting a fallback anchor function is deprecated and will be removed in a future release.
             File ".venv/lib/python3.12/site-packages/mkdocstrings/plugin.py", line 190, in on_config
               autorefs.get_fallback_anchor = self.handlers.get_anchors
             File ".venv/lib/python3.12/site-packages/mkdocs_autorefs/plugin.py", line 130, in get_fallback_anchor
               warn(

To Reproduce

mkdir mre
cd mre
uv init .
vim mkdocs.yml # see content below
mkdir docs
touch docs/index.md
uv add mkdocs
uv add mkdocstring[python]
uv run mkdocs serve

content of mkdocs.yml:

site_name: Deprecation

nav:
  - Home: index.md
plugins:
  - search
  - mkdocstrings:
      handlers:
        python:
          paths: ["."]

Leaving out paths results in another issue I will not discuss in this issue.

Content of index.md:

::: hello

Expected behavior

For the moment this works fine (ignoring the page of the mre doesn't render any useful, because of missing docstring.) but may cause issues in the future.

I actually oversaw the deprecation multiple time today, so...

Environment information

python -m mkdocstrings_handlers.python.debug  # | xclip -selection clipboard

• System: Linux-6.12.8-arch1-1-x86_64-with-glibc2.40
• Python: cpython 3.12.8 (/home/matti.kaupenjohann/05_Coding/python/mkdocs_MRE/.venv/bin/python)
• Environment variables:
• Installed packages:
  • mkdocs v1.6.1
  • mkdocstrings v0.27.0
  • mkdocstrings-python v1.13.0
  • griffe v1.5.5

Additional context

[pawamoy]

Hi @MaKaNu, yes this is expected and the deprecation warning will be removed with next version of mkdocstrings-python 🙂 Closing, feel free to comment further!

[AbdullahK-1QBit]

I am still seeing these warnings with the latest versions of the packages

mkdocs                 1.6.1
mkdocs-autorefs        1.4.1
mkdocs-get-deps        0.2.0
mkdocstrings           0.29.1
mkdocstrings-python    1.16.10

Did you mean this will be fixed in mkdocstrings-python version 1.17.

[pawamoy]

IIRC I pushed back a little on removing these warnings, but shouldn't take long anymore 🙂