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)

OK, so two things:

1) Sorry my last message came across as ANSI, as that was unintended. I think by using the ANSI editor to include the extended ASCII characters in my example, I must have posted the message as ANSI inadvertently.

2) I found several older messages on the topic on this and on other networks, and yeah, it would seem printing extended ASCII characters to the terminal in Python 3 is indeed problematic in Mystic.

Oh well. I guess I'll just hold off on trying to do any Python 3 stuff. I almost want to scrap Python entirely for this reason and learn MPL stuff instead.

┌ codefenix - dawnCHAOTIC
│ telnet://conchaos.synchro.net:2300
│ ssh://conchaos.synchro.net:2200


... If at first you don't succeed, blame your parents!

--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: dawnCHAOTIC: telnet://conchaos.synchro.net:2300 (21:4/141.1)