Does anyone have a working Ubuntu setup for Mystic Python (mpy) that uses modules installed via Pip? If so, can you share your env variable setup?

Python 2.7 itself is working for me, but modules are not found when running under mystic. Helpful error message says to check the wiki -- looks like it's env variables that need to be set. I've set:

export PYTHONPATH=/home/mysticuser/.local/lib/python2.7

But that doesn't seem to work. Used the same path in mystic's GENERAL CONFIG python setting as well...

Cheers and thanks!

|04þ |12Alpha |04þ
|03Corporation X BBS|08........|11corpxbbs.com:2323|08...........|07Mystic |03The Drunken Gamer BBS|08....|11thedrunkengamer.com:8888|08....|07Talisman

--- Mystic BBS v1.12 A47 2021/01/05 (Linux/64)
* Origin: Corporation X BBS (21:4/158)

On 21 Jan 2021, Alpha said the following...

Does anyone have a working Ubuntu setup for Mystic Python (mpy) that uses modules installed via Pip? If so, can you share your env variable setup?

I don't have any advice there, but g00r00 just updated the prealphas (but not for the Pi yet) with a new Python engine and had this to say:

The new engine should handle errors better, do better at cleaning up bad
code (if for example you don't call a msg_close for example on an open g0>

message base, it should detect it and close it). It should also run g0> without any of the environment nonsense we had to do with recompiling in g0> the past, and overall it should be more stable across many platforms.

Not sure if this would help you out?


Jay

--- Mystic BBS v1.12 A47 2021/01/16 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

I don't have any advice there, but g00r00 just updated the prealphas
(but not for the Pi yet) with a new Python engine and had this to say:

Thanks, Warpslide! I just updated the pre-alpha! Sounds promising :)

I've decided for now to abandon external modules until I actually need them (and I may not even need them) for my little game. Just using the 'regular' python functions and the mystic_bbs module will probably get me there... Pretty














sure it's an env issue I can eventually solve.

OH and I just realized how game-changing embedded python is for Mystic customization. I'd never really had a desire to learn MPL. But I'd been banging














my head on coding a 'proper' door using Golang and in about 5 minutes accomplished with embedded python what took me a week to do/learn using Go. Granted, it'll only run on Mystic systems, so there's a trade-off I suppose... But still, cool.

Cheers!

|04þ |12Alpha |04þ
|03Corporation X BBS|08........|11corpxbbs.com:2323|08...........|07Mystic |03The Drunken Gamer BBS|08....|11thedrunkengamer.com:8888|08....|07Talisman

--- Mystic BBS v1.12 A47 2021/01/21 (Linux/64)
* Origin: Corporation X BBS (21:4/158)

I don't have any advice there, but g00r00 just updated the prealphas
(but not for the Pi yet) with a new Python engine and had this to say:

The new engine should handle errors better, do better at cleaning up
code (if for example you don't call a msg_close for example on an open

message base, it should detect it and close it). It should also run

without any of the environment nonsense we had to do with

recompiling in g0> the past, and overall it should be more stable
across many platforms.

Just to follow-up on this -- new pre-alphas solve the python environment issues












for me! Although the release focuses on Python 2 (G@), Python 3 (GZ) now works for me as well! Woo-hoo!

Cheers,

|04þ |12Alpha |04þ
|03Corporation X BBS|08........|11corpxbbs.com:2323|08...........|07Mystic |03The Drunken Gamer BBS|08....|11thedrunkengamer.com:8888|08....|07Talisman

--- Mystic BBS v1.12 A47 2021/01/21 (Linux/64)
* Origin: Corporation X BBS (21:4/158)