[Feature]: A Second Argument to `pyapi()`

[angelcaru]

Is your feature request related to a problem? Please describe. When using pyapi(), often the only way to get what you want is using string interpolation. But this is very error-prone.

Describe the solution you'd like The second (optional) argument to pyapi() would be a namespace where to execute the code. This would also get rid of the ugly output variable. Example:

ns = {}
ns["my_var"] = 69
pyapi("
assert isinstance(my_var, int) # Radon values converted to native Python values. Special care would be needed in the case of functions.
assert my_var == 69
my_output = 'abc'
", ns)
assert ns["my_output"] == "abc" # Python values are converted back to Radon values. Once again, special care would be needed in the case of functions.

Describe alternatives you've considered I also considered making the second argument be anything, which you could access through a magical input variable (similar to output). But you would often end up with the same pattern of passing a List or HashMap and pulling the values out. It's just better to do that directly

[Almas-Ali]

Total disaster when converting Python >--< Radon objects! Every trial is crashing!

[Almas-Ali]

Can you give it a try?

[angelcaru]

Yeah, sure

[Almas-Ali]

Thanks!

[angelcaru]

Not done yet, but I'm getting somewhere...

[Almas-Ali]

I think we need two functions, which will map all nested objects and convert to Radon to Python and Python to Radon.

[angelcaru]

That's exactly what I'm doing!

[Almas-Ali]

Great! Hopefully this will work.

[angelcaru]

I got it working, but one of the test cases is failing :( Hopefully I'll be able to fix it

[angelcaru]

I fixed it :)