Dear people, when trying to build a documentation of modules, which import packages located in some system path, where sphinx cannot find them (because the path may not be listed in conf.py), the build fails with an "ImportError: No module X found", even though these packages may not be subject to the intended documentation (like, for example numpy or theano). When I add the system path to the configuration, everything runs smoothly.
Since I'm fairly new to sphinx I was wondering, if there is a way to handle these situations, because working in a project with many people using heterogeneous python distributions can then create a problem: If distribution paths do not match or imported packages do not exist, because the specific user works on a part of the project not relying on those packages, the documentation does not get built. Right now, we use user-specific paths guarded by try-catch-blocks, which seems like the least favorable solution. Hope, you can help me out! Thanks and best regards, Per -- You received this message because you are subscribed to the Google Groups "sphinx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sphinx-users. For more options, visit https://groups.google.com/d/optout.
