Subj : Re: g00r00 - a49 32-bit alpha
To   : cr1mson
From : Dan Clough
Date : Tue Jan 14 2025 04:19 pm

-=> cr1mson wrote to All <=-

 cr> g00r00-

 cr> Hi, this is cr1mson from Raiders Inc BBS... I've been using Mystic for
 cr> awhile now.  I've recently been using an RPi 3B+.  I ported Mystic a47
 cr> over to it and upgraded to the prealpha a49 (32-bit).  I installed the
 cr> libpython2.7.so.1 and Python 2.7 with a few pip modules.  Trying to run
 cr> a mod that works fine with a47 and a48, I've run into this warning:

 cr> sys:1: RuntimeWarning: Python C API version mismatch for module
 cr> mystic_error: This Python has API version 1013, module mystic_error has
 cr> version 2127954933

 cr> I didn't get this warning in a47 or a48, however, with a48, I couldn't
 cr> get my Mystic to do successful polls AND use the cl3441 SSH at the same
 cr> time.  One would work and one would fail, but the mod worked fine, so I
 cr> upgraded to a49.

 cr> Has anyone else had this warning with threatsentry (python 2.7 mod) or
 cr> anything like it?  g00r00 if you're listening, please please get an rpi
 cr> 64-bit out of the prealpha as this might solve my issue.

 cr> Any ideas I could do, g00r00 in the meantime?  I've rebuilt Python 2.7
 cr> and the lib dev files, put the libpython2.7 in my mystic and specified
 cr> it in the mystic cfg as well as even installed a brand new mystic a49
 cr> with just the basics of the libpython, mystic a49 and the mod, but
 cr> still getting the exact error.

He's not around, and hasn't been.

There was much talk a while back about needing to use Python 3.x for 
more recent Mystic stuff, as I recall.  I also think I remember seeing 
that doing so broke a lot of other stuff.  So I'm not sure there is a 
good solution at the moment.



.... Behind every great man is an amazed mother-in-law!
=== MultiMail/Linux v0.52
--- SBBSecho 3.23-Linux
 * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

.