I realize this isn't entirely the responsibility of the Pangolin team, but it's a simple fix and I believe it improves the clarity and manageability of this package, so here's the story:
Nextstrain's tools and ecosystem have been integrating with Pangolin more deeply recently. It's common to need to run ncov and/or ncov-ingest alongside a pangolin installation.
The pango-designation package as it stands right now installs a top-level module called utils when installed via pip. As far as I can tell the modules in this package aren't referenced by anything else in the ecosystem, and the presence of this top-level module breaks several of the tools in the ncov-ingest package which has its own internalutils module.
I think that moving the pango-designation utils module under the pango-designation module, or not installing it at all will help improve interoperability with other tools, and reduce confusion about where a system-wide package called utils is coming from.
I realize this isn't entirely the responsibility of the Pangolin team, but it's a simple fix and I believe it improves the clarity and manageability of this package, so here's the story:
Nextstrain's tools and ecosystem have been integrating with Pangolin more deeply recently. It's common to need to run ncov and/or ncov-ingest alongside a pangolin installation.
The pango-designation package as it stands right now installs a top-level module called
utils
when installed via pip. As far as I can tell the modules in this package aren't referenced by anything else in the ecosystem, and the presence of this top-level module breaks several of the tools in thencov-ingest
package which has its own internalutils
module.I think that moving the pango-designation utils module under the pango-designation module, or not installing it at all will help improve interoperability with other tools, and reduce confusion about where a system-wide package called
utils
is coming from.