is 0.9.0 and be sure your run python with the full path: cd ~/.snap/snap-python/snappy You should try the suggested steps to build a binary wheel using your python-3.6.
This is not surprising, as they want it to run on many macosx versions, but you generally can’t safely run macosx_10_12 packages in python built for 10_9. This indicates the binary wheels was build for macosx_10_12, but it looks like built python-3.6 using macosx_10_9. The bundled jpy binary wheels are: % jar tf /home/gwhite/snap/snap/modules/org-esa-snap-snap-python.jar | grep 'jpy.*-macos' I am trying to run it on MacBookPro mac OSCatalina version 10.15.6.īut snappyutil.log mentions macosx_10_9. The third party packages may be a better option if you are planning to make heavy use of python with ESA SNAP snappy and expect to need additional python libraries.
Anaconda python’s older versions have been problematic because they don’t update them for newer versions of macOS. If the python-3.6 doesn’t run on your version of macOS or ESA SNAP snappy still can’t be configured, you may be able to install python-3.6 using third party packages such as macports or homebrew. Any executable in one of these locations can be executed without specifying a complete path.” (note that many web documents suggest changing the PATH, so use caution). See: Apple Shell Scripting Command Line Primer.įor macOS the PATH is one of the “Special Shell Variables”, t “A colon-delimited list of locations where trusted executables are installed. If that works, you can continue with the checks from Configure Python to use the SNAP-Python snappy interface, but always run python3 using the full path (e.g., /usr/local/bin/python3). I think ’s Python-3.6 will provide /usr/local/bin/python3, so in a terminal, /usr/local/bin/python3 to verify that you are getting a 3.6 version and that it actually runs on your more recent macOS version, then change the working directory to the /bin and run.