What happened?
I'm a bit confused by some behavior when using rv.runtime.eval with the export_utils module.
For sake of a simple example, take e.g.
import rv
print(rv.runtime.eval('export_utils.tempSessionName("rv")', ["export_utils"]))
This would just error:
Traceback (most recent call last):
File "<string>", line 2, in <module>
Exception: Exception thrown while calling runtime.eval
But if I run this prior:
rv.runtime.eval('runtime.load_module("export_utils");', [])
Then suddenly everything is fine, and it prints the path of the temp session as well.
Why do I need this separate call first? And how can I run export_utils module directly in a single runtime eval regardless of whether I've previously enforced the load of the module?
List all the operating systems versions where this is happening
Windows 11, OpenRV_3.0.0+f85b7da-win64
On what computer hardware is this happening?
Nvidia Geforce RTX 4070 SUPER , 128 GB ram
Relevant console log output
INFO: Traceback (most recent call last):
INFO: File "", line 2, in
INFO: Exception: Exception thrown while calling runtime.eval
Environment variables
No response
Extra information
No response
Code of Conduct
What happened?
I'm a bit confused by some behavior when using
rv.runtime.evalwith theexport_utilsmodule.For sake of a simple example, take e.g.
This would just error:
But if I run this prior:
Then suddenly everything is fine, and it prints the path of the temp session as well.
Why do I need this separate call first? And how can I run
export_utilsmodule directly in a single runtime eval regardless of whether I've previously enforced the load of the module?List all the operating systems versions where this is happening
Windows 11, OpenRV_3.0.0+f85b7da-win64
On what computer hardware is this happening?
Nvidia Geforce RTX 4070 SUPER , 128 GB ram
Relevant console log output
Environment variables
No response
Extra information
No response
Code of Conduct