Hi Antonio, Thanks for the diagnostics data.
> I'm working with a virtual environment. Ah, that's the crux. I assume you've used something like `python3 -m venv --system-site-packages`. That happens to be not compatible with how PyMOL finds $PYMOL_PATH, it uses `sys.prefix` for that which now points to your virtual environment. Here some options which should all solve the issue: 1) Place the license file at $HOME/.pymol/license.lic 2) Export PYMOL_PATH=/home/my_user/pymol/share/pymol before importing the `pymol` module (can be done with `os.environ['PYMOL_PATH'] = ...` from your Python script). This option I would avoid if possible, better not to hard-code any paths in your script. 3) Use conda environments instead of venv. That's my preferred solution. . $HOME/pymol/bin/activate conda create -p $HOME/envs/dqn_pymol2 schrodinger::pymol conda activate $HOME/envs/dqn_pymol2 Cheers, Thomas -- Thomas Holder PyMOL Principal Developer Schrödinger, Inc. _______________________________________________ PyMOL-users mailing list Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net Unsubscribe: https://sourceforge.net/projects/pymol/lists/pymol-users/unsubscribe
