-
Notifications
You must be signed in to change notification settings - Fork 53
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
Broken imports #893
Comments
I put here an excerpt of the console output for
|
What we have said in the past is that each institute handles their dependencies for site specific code. This as versioning and even availability of certain modules outside of the institute might not be easily handled. This creates a problem for a tool like sphinx that needs to import the modules in order to function. When we used sphinx in the past we said that we would not run it on site specific code (as far as I remember), which I agree is a bit of a pity. I guess the problem could partially be solved by using One solution would perhaps, orthwise, be to add a section in the |
Ah, that's an idea I have not considered. Maybe that is a solution for things that can not be solved in a cleaner way (by fixing the code). But I do not know if Sphinx can be configured easily to ignore some sub packages. Seems like it is an allow-list, rather than a blocklist. |
Building the documentation with
sphinx-build
seems to uncover a whole range of broken imports. Some seem to be due to missing dependencies (see: #885), but some other seem to be due to bugs in the code (or abandoned code). Those need to be investigated, and hopefully fixed.The text was updated successfully, but these errors were encountered: