Explain _loci proxy importing and pdoc

Author: ehrenfeu

src/imcflibs/imagej/_loci.py

@@ -7,6 +7,20 @@
 
 By stashing this into an internal submodule only checks on this specific
 (minimalistic) file will fail but remain operational for the other code.
+
+So why are the other imports in here then?
+
+This was a conscious decision as it seems to be confusing that *some* parts from
+the `loci` package need to be imported from the `imcflibs.imagej._loci`
+sub-module while others are imported directly. Instead we're simply importing
+proxy-style all loci components through the file here.
+
+NOTE: the actual import of `ImporterOptions` still requires the `# pdoc: skip`
+pragma to work with the documentation generation scripts, e.g.
+
+```
+from ._loci import ImporterOptions  # pdoc: skip
+```
 """
 
 from loci.plugins import BF

src/imcflibs/imagej/bioformats.py

@@ -14,7 +14,8 @@
 
 from ij import IJ
 
-from ._loci import BF, ImporterOptions, ImageReader, Memoizer
+from ._loci import ImporterOptions  # pdoc: skip
+from ._loci import BF, ImageReader, Memoizer
 
 from ..pathtools import gen_name_from_orig
 from ..log import LOG as log