I actually do not have anything on the bashrc or bash_profile. I use a module system and my bash environment never loads something by default. Though, when I installed the master update, there was another PYTHONPATH set for another program I was using. It may be why I got this persistent PYTHONPATH error even when I forced to reinstall the worker. But I am sure any non linux geek may fall into this trap very easily. As @olibclarke said, if these lines do not have any disadvantages for using cryosparc, they can be included in the upcoming updates. I am sure it will fiddle with other program’s python path usage.