ParaView 5.9 can't load python 3.8 libraries on MacOS Catalina

That’s possible to load the library from Python in Terminal and I added the key “” to the plist but without success:

    import geopandas as gpd
  File "/usr/local/lib/python3.8/site-packages/geopandas/", line 3, in <module>
    from geopandas.geoseries import GeoSeries  # noqa
  File "/usr/local/lib/python3.8/site-packages/geopandas/", line 9, in <module>
    from pyproj import CRS, Transformer
  File "/usr/local/lib/python3.8/site-packages/pyproj/", line 49, in <module>
  File "/usr/local/lib/python3.8/site-packages/pyproj/", line 10, in <module>
    from pyproj._network import (  # noqa: F401
ImportError: dlopen(/usr/local/lib/python3.8/site-packages/pyproj/, 2): no suitable image found.  Did find:
	/usr/local/lib/python3.8/site-packages/pyproj/ code signature in (/usr/local/lib/python3.8/site-packages/pyproj/ not valid for use in process using Library Validation: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?)

The library file can be signed by trusted self-signed code-signing certificate without any changes (the Python library still doesn’t work in ParaView):

codesign -vvvv /usr/local/lib/python3.8/site-packages/pyproj/
/usr/local/lib/python3.8/site-packages/pyproj/ valid on disk
/usr/local/lib/python3.8/site-packages/pyproj/ satisfies its Designated Requirement

How did you build/obtain ParaView? The official packages or a custom build?

@ben.boeckel The original build is used with this launch script:



It would seem that some Apple library got into your /usr/local (Homebrew?) software somehow. I really don’t know how Library Validation works or how we could fix it beyond signing and noterizing ParaView itself (which I believe we do? @cory.quammen). Not signing ParaView isn’t really a practical option though…

We do sign the ParaView binaries. I have no idea whether what you are trying to do (pull in a external Python package) is possible, but I strongly suspect it is not. It’s challenging enough to get the known executables and libraries signed and working in the ParaView Mac binaries in the first place.

@ben.boeckel @cory.quammen ParaView 5.8 doesn’t work now:
“” cannot be opened because the developer cannot be verified.
ParaView 5.7 with python 2.7 and the same Python modules works fine. Looks as your recent macOS builds are broken…

This ParaView plugin is used:

I wrote it for ParaView 5.7 with Python 2.7 and it’s works fine. It WAS ok for ParaView 5.8 some time ago. Also, it was usable for ParaView 5.9 on MacOS Mojave but it doesn’t work on MacOS Catalina. And, probably, the situation is the worst on recent MacOS BigSur. is a nightly build, and we don’t sign nightlies.

You can work around the message “cannot be opened because the developer cannot be verified” by allowing the executable to run by going to System Preferences -> Security & Privacy and under “Allow apps downloaded from:” click the radio button that says “App Store and identified developers.” When you run again, it might deny you, so you’ll need to explicitly allow that to run.

Keep in mind that starting with ParaView 5.9, we are including Python 3.8 in the ParaView binaries on macos. Previously, we relied on the system Python installed on macos.

@cory.quammen Hmm, I already have the option enabled to launch applications from identified developers. But on MacOS Catalina I can’t run this one.
Thanks, I remember about this great change… it was very hard to maintain ParaView plugins with multiple dependencies for obsolete Python 2.7. Actually, I don’t understand why Homebrew python 2.7 libraries work with old ParaView but Homebrew python 3.8 libraries produce system validation error even signed by trust self-signed certificate.