unfortunatley, I don't think this is a great candidate for nixpkgs (personal project, no tests), however, https://github.com/nix-community/NUR would be a good candidate if you wanted to share with others.

Are you sure? It's used within home-assistant, which we have packaged.

I'd be happy to submit a PR to NUR if that's the place to put it. However as @Mic92 pointed out home-assistant depends on this library to get the weather from the met.no service. Wouldn't HA be much harder to use when parts of it depend on NUR?

I don't currently see it in nixpkgs.

I would be okay with doing pythonImportsCheck on the majority of importable modules. Just want to ensure that it's actually usable when doing dependency bumps. Unit tests are much more preferable as they give some notion of correctness.

I would be okay with doing pythonImportsCheck on the majority of importable modules.

I don't quite get that. What does pythonImportsCheck do? greping for it didn't really enlighten me. Seems like most packages that use it put themselves in there.

Should I do something like this?

pythonImportsCheck = [ "pymetno"];

pythonImportsCheckPhase () {
    echo "Executing pythonImportsCheckPhase"

    if [ -n "$pythonImportsCheck" ]; then
        echo "Check whether the following modules can be imported: $pythonImportsCheck"
        ( cd $out && eval "@pythonCheckInterpreter@ -c 'import os; import importlib; list(map(lambda mod: importlib.import_module(mod), os.environ[\"pythonImportsCheck\"].split()))'" )
    fi
}

It will essentially do python -c 'import XXXX' to each of the modules you list. This will at least cause the python interpreter to import/evaluate all the modules that it needs at the beginning of the files.

Let's go with this solution.

I have updated this to use pythonImportsCheck. Thanks for the explanation @jonringer.