Forcing a local Python installation leads to incorrect configuration of SNAP

Just noticed during my SNAP (beta 7.0) installation that when I force SNAP to use an already installed Python distribution on Linux, the application is not configured correctly. The SNAP installer finishes without errors, but when I try to run SNAP (both in a shell as well as through a regular shortcut), JRE starts but SNAP does not get initialized (even no fancy splash screen).

After uninstalling and skipping the Python path forcing when reinstalling, things work well.

I do not know what the specific source for this behavior is, but maybe good to be aware of.

Cheers, Jelte.

Help is underway! Problem will be fixed in next beta. Sorry for the inconvenience. (

To configure SNAP with Python you can now use the new bin/snappy-conf tool.

1 Like