This in the only source of data that we can't serve via OCI-backed or Anaconda.org-backed info/ metadata directly because it requires a global package search. We need to figure out how to present these maps without relying on libcfgraph-like setups (i.e. not another JSON in a repo?).
One way is to reutilize the files-to-artifacts mapping and compute the import-maps on the spot, because they can be inferred by the location of __init__.py modules, mostly.
jaimergp
commented
3 months ago
Depends on #54
This in the only source of data that we can't serve via OCI-backed or Anaconda.org-backed
info/metadata directly because it requires a global package search. We need to figure out how to present these maps without relying onlibcfgraph-like setups (i.e. not another JSON in a repo?).One way is to reutilize the files-to-artifacts mapping and compute the import-maps on the spot, because they can be inferred by the location of
__init__.pymodules, mostly.