OK, so scverse-doc now almost exists. Should we move generic docs stuff there? E.g. some or all of what was added in #60 is not related to any runtime feature scverse-misc offers.
I wonder how we should handle it:
should scverse-doc depend on scverse-misc[sphinx] and load its extension? Then people could choose:
dependency-groups.docs = [ "scverse-doc" ] and extensions = ["scverse_doc"] gives them all scverse-doc features and all the scverse-misc features they activate in their project.dependenciesdependency-groups.docs = [ "scverse-doc" ] and extensions = ["scverse_doc.foo"] gives them only the subextensions they want (like scanpydoc)dependency-groups.docs = [ "scverse-misc" ] and extensions = ["scverse_misc.sphinx_ext"] give them just docs support for the runtime features, no additional docs features
but we’ve already deviated from that with #60 …
OK, so scverse-doc now almost exists. Should we move generic docs stuff there? E.g. some or all of what was added in #60 is not related to any runtime feature scverse-misc offers.
I wonder how we should handle it:
should
scverse-docdepend onscverse-misc[sphinx]and load its extension? Then people could choose:dependency-groups.docs = [ "scverse-doc" ]andextensions = ["scverse_doc"]gives them all scverse-doc features and all the scverse-misc features they activate in theirproject.dependenciesdependency-groups.docs = [ "scverse-doc" ]andextensions = ["scverse_doc.foo"]gives them only the subextensions they want (like scanpydoc)dependency-groups.docs = [ "scverse-misc" ]andextensions = ["scverse_misc.sphinx_ext"]give them just docs support for the runtime features, no additional docs featuresbut we’ve already deviated from that with #60 …