Update library import checks

[eirikurj]

Purpose

Currently, the library import check suppresses useful information why the library could not be imported. This PR updates the import check to print out the full error message.

Expected time until merged

No rush, but should not take long.

Type of change

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (non-backwards-compatible fix or feature)
• [ ] Code style update (formatting, renaming)
• [x] Refactoring (no functional changes, no API changes)
• [ ] Documentation update
• [ ] Maintenance update
• [ ] Other (please describe)

Testing

Compile the module with and without the fix, with a broken library.

Checklist

• [x] I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
• [ ] I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
• [ ] I have run unit and regression tests which pass locally with my changes
• [ ] I have added new tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation

[codecov[bot]]

Codecov Report

Merging #67 (77eb9d4) into main (262099a) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #67   +/-   ##
=======================================
  Coverage   79.43%   79.43%           
=======================================
  Files           4        4           
  Lines         423      423           
=======================================
  Hits          336      336           
  Misses         87       87           

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more