Question about Python dependency resolution when using the monrepo plugin with mkdocstrings plugin

Hello there,

We make use of a plugin called **mkdocstrings** to generate documentation for the source code. This plugin loads the different Python libraries mentioned in the source code during the documentation generation process. As a result of this, there are Python dependency resolution issues that we encounter when using the monrepo plugin in a root repository . If the mkdocs.yaml file in the root repository references multiple mkdocs.yaml files from different repositories, we run into dependency resolution errors as there are conflicting dependency requirements in the different repositories.

The code in each of the different repositories uses different versions of the same Python module. Hence, the issue.
I am wondering that this must be an issue at a lot of organizations.
How is this overcome elsewhere?

To overcome this, we were thinking that the docs folder in each of the different repositories should be processed independently and the output of the mkdocs build command should be copied to some place in the root repository and then have mkdocs somehow assemble the documentation. I am not sure if this is even possible. If someone has already done this, please respond back.

Thanks,
Kiran Hegde

Start by reviewing the root mkdocs.yaml references, the separate repositories' mkdocs.yaml files, and the docs folders involved in the mkdocs-monorepo-plugin setup. Reproduce the conflicting Python dependency requirements during mkdocs build, then determine whether independently building each docs folder and assembling the outputs can be supported; the issue does not define a settled implementation or completion criteria.

Written by the indexing model from the issue text.