Been experimenting with Python in my spare time ov
er here on my Mystic board,version
1.12 A48 on Windows 10
64-bit.Consider the followi
ng Python code:import mystic
_bbs as bbsprint ( chr(248
) )bbs.writeln ( chr(
248) )If I run this scrip
t from mystic as a Python 2.7.18
script, the output, whichis intend
ed, is:øøHowever, whe
n run in Mystic as a Python 3.12.6 script, the output becomes:
øøSeems the bbs.writ
eln function is not pumping the correct extended ASCII
characters to the BBS terminal. Guessing it h
as to do with encoding in Python3.x
versus Python 2.7. Characters
in the range below 128 display just fine.
Is there a trick to getting Python 3.x to d
isplay extended ASCII in theterminal, or
is this just something that doesn't work (yet
)? I've come tounderstand that P
ython 2.7 is still widely used in M
ystic, and maybe this isjust one of the reasons w
hy?
Ú codefenix - dawnCHAOTIC
³
telnet://conchaos.synchro.net:2300
³
ssh://conchaos.synchro.net:2200
... The dog ate my .REP packet
--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: dawnCHAOTIC:
telnet://conchaos.synchro.net:2300 (21:4/141.1)