Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implicit namespace packages do not generate documentation #298

Open
Yoshanuikabundi opened this issue Jul 21, 2021 · 6 comments
Open

Implicit namespace packages do not generate documentation #298

Yoshanuikabundi opened this issue Jul 21, 2021 · 6 comments

Comments

@Yoshanuikabundi
Copy link

Hi! Thanks for your work on this package, it really saved me from a lot of autosummary-related misery.

I've noticed a bug: the autoapi_python_use_implicit_namespaces option is fantastic, but it doesn't create a page for implicit namespace packages. If I have a Python project with the following file layout:

- package1/
    - package2/
        - __init__.py
        - module1.py
        - package3/
            - module2.py
        - package4/
            - __init__.py
            - module3.py

autoapi with autoapi_python_use_implicit_namespaces=True generates the following documentation:

- package1/
    - package2/
        - index.rst
        - module1/
            - index.rst
        - package3/
            - module2/
                - index.rst
        - package4/
            - index.rst
            - module3/
                - index.rst

In other words, only modules and packages defined with __init__.py files (explicit packages) are documented with an index.rst. Implicit namespace packages, those defined according to PEP420 without __init__.py, are not documented. This leads to Sphinx warnings about their children not being included in any toctree.

According to PEP420, implicit namespace packages are true packages. The user of the library can't tell the difference without digging. I think implicit namespace packages therefore should be documented as true packages, whose members include only their child modules and packages. Ideally they would also have a docstring that suggests that they're implicit namespace packages!

So in my above example, my expected output would be:

- package1/
    - index.rst
    - package2/
        - index.rst
        - module1/
            - index.rst
        - package3/
            - index.rst
            - module2/
                - index.rst
        - package4/
            - index.rst
            - module3/
                - index.rst

Thanks!

@Yoshanuikabundi
Copy link
Author

Oh! Also this is on autoapi 1.6.0, which is the latest available on conda-forge. Sorry if this has been fixed since then! Would be great to get that updated.

@kaxil
Copy link

kaxil commented Mar 14, 2022

We are facing the same issue, any plans to fix this?

@jazzblue
Copy link

jazzblue commented Aug 11, 2022

Same here, facing same issue: autoapi_python_use_implicit_namespaces = True seems like not working and I also wonder if there are any plans to fix it?

@kaxil
Copy link

kaxil commented Aug 12, 2022

Same here, facing same issue: autoapi_python_use_implicit_namespaces = True seems like not working and I also wonder if there are any plans to fix it?

We used this custom template as a workaround and it has worked well for us. Check API reference at https://astronomer-providers.rtfd.io/

@chrisyeh96
Copy link

Still facing the same issue, as of autoapi version 2.1.1.

@mezhaka
Copy link

mezhaka commented Nov 22, 2023

For those who land here from a search engine: there's a --implicit-namespaces option in the sphinx-apidoc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants