TID: Mystic BBS 1.12 A48   
   MSGID: 1:142/104 ea59d19d   
   REPLY: 1:134/303 4bf6005f   
   TZUTC: -0400   
   On 13 Oct 2022, Travis Mehrer said the following...   
       
    TM> On 06 Oct 2022, Clive Reuben said the following...   
    TM>     
    TM>  CR> Hey g00r00, I was wondering if you knew of a reason that embedded   
    TM>  CR> python3 would not be able to print extended characters... e.g. if I d   
    TM>  CR>    
    TM>  CR> "write(chr(177))" it will print garbage....    
    TM>    
    TM> I can somewhat confirm this; however, it's worth noting that since   
    TM> Python 3 uses unicode by default chr() doesn't behave the same as in   
    TM> Python 2. chr() will output the unicode character of that number.   
    TM>    
    TM> In a terminal you could use something like b'xc0'.decode('cp437') (sorry   
    TM> that's just the hex code for the character I was testing with) to output   
    TM> an ANSI character. But this also doesn't seem to output as expected with   
    TM> mpy.   
      
   Hey Travis, That's a very good point and would tend to confirm my suspicion.   
   Thanks, for the response!   
      
   -seeLive   
      
   ... The dreams you'd hear if the streets could talk.   
      
   --- Mystic BBS v1.12 A48 2022/07/15 (Raspberry Pi/32)   
    * Origin: oNyX bBs - onyxbbs.mywire.org:2300/2200 (1:142/104)   
   SEEN-BY: 1/19 123 15/0 16/0 19/37 80/1 90/1 105/81 106/201 120/340   
   SEEN-BY: 123/130 131 129/305 142/104 799 153/7715 203/0 218/700 221/0   
   SEEN-BY: 226/30 227/114 229/110 111 112 113 206 275 317 400 424 426   
   SEEN-BY: 229/428 452 470 550 664 700 240/5832 266/512 282/1038 292/854   
   SEEN-BY: 317/3 320/119 219 319 322/0 757 325/304 342/200 396/45 460/58   
   SEEN-BY: 633/280 712/848   
   PATH: 142/104 320/219 229/426