Subj : Re: Mystic upgrade confusion
To   : DustCouncil
From : DustCouncil
Date : Fri Jul 02 2021 10:13 pm

Fixed the Python issue after a search through this echo.

From an exchange about a month ago:

The Godfather reported that he was having Python problems as well, and Warpslide responded that the Python paths in Configuration -> General Settings were set to Windows paths.  At some point in the upgrade process, this happened to me as well.

This turned out to be my problem as well.  I don't recall just glossing over those settings or if they are new, but as I am running Linux, blanking out that setting worked for me as it now access from the default location on my Linux system.

Curiously, pointing the directory to my actual libpython2.7.so.1.0 file, or to do the directory it is in, did not work for some reason.

Blank works.

But these do not, for some reason.  As I run Ubuntu, I had to do the compile-with-swtiches procedure from the Wiki.

 /usr/local/bin/python
 /usr/local/bin/python/libpython2.7.so.1.0

Just including it here in case anyone else has this issue.

--- Mystic BBS v1.12 A47 2021/06/28 (Linux/64)
 * Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

.