Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error importing module: No module named 'matplotlib._docstring' #902

Closed
ferokko opened this issue Nov 15, 2023 · 3 comments
Closed

Error importing module: No module named 'matplotlib._docstring' #902

ferokko opened this issue Nov 15, 2023 · 3 comments

Comments

@ferokko
Copy link

ferokko commented Nov 15, 2023

Hi all,

I am using the porespy library on a databricks environment, python Python 3.10.12. I have been using it for 2 years now, but in the last 6 months I didn't use it anymore.

I need to use it again now and I needed to create a new compute instance on databricks. I installed the library in the compute cluster like any other library, version 2.3.0. The installation is via pip.

In the notebook code, during the import phase I get this error

import porespy as ps
ModuleNotFoundError: No module named 'matplotlib._docstring'

Any idea why?

Thanks!

@jgostick
Copy link
Member

The problem is coming from openpnm, which porespy installs. The "root" problem is that your databricks instance seems to be using an old matplotlib version. We fixed this in openpnm, but our fix was not general enough to handle new and old versions of openpnm. I have patched this on the dev branch of openpnm but had not merged it into a release yet. I will do today.

PMEAL/OpenPNM#2857

@ferokko
Copy link
Author

ferokko commented Nov 16, 2023

Hi @jgostick , thanks a lot! Indeed I saw on openpnm GH that there was the try/catch in the _doctxt function but the version I am using on the cluster still shows the older version. Will this be integrated into the porespy version 2.3.0 on the pypi ?

@jgostick
Copy link
Member

I was going to do it today but the windows builds are all failing for unknown reasons. I was hoping this problem would fix itself (i.e. a github problem), but I'm still waiting. I will merge asap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants