fix for issue #437

[russtoku]

I think I've solved the problem with embedded newline characters in Python source code. All of the examples in dev/python/sandbox.py evaluate correctly. I haven't tried it with other Python files yet. Just wanted to get something working for others to try on their code.

[Olical]

So definitely an improvement! Although I've found another edge case 😬 I'm worried there will be many while we have to mess with new lines in any capacity.

def newline_in_function_bug():
    return 'hey\n\n' + "\\n" + '\n' + 'ho'

newline_in_function_bug() # 'hey\n\n\nho'

The \\n should result in a \n being printed inside the string, but not an actual newline, a separate \ and n character if I'm not mistaken? I'll have a look at your changes some more and see if I can add to it to catch this too.

Really I need to actually rewrite the stdio support from the ground up so we can deal with these things in a better way.

[Olical]

The output from a plain Python REPL:

>>> def newline_in_function_bug():
...     return 'hey\n\n' + "\\n" + '\n' + 'ho'
... 
>>> newline_in_function_bug()
'hey\n\n\\n\nho'

[Olical]

[Olical]

Cunning plan, executed. Base64 encode the source in Lua, decode it within the REPL, never deal with encoding issues again. 🚀

We still have two eval styles depending on if you're evaluating an "expression" or not... maybe we can just delete those now and just have the one system?

[russtoku]

Awesome! Many thanks!