Jeff Long

Other places in GRC that do `eval()` pass in a local namespace. If we do that, and specify `__builtins__ = None`, which we should probably be doing elsewhere, then it...

The eval should at least use a local namespace. I don't know to what degree that helps, but let's not be less "secure" than the rest of the system. Agree...

So, would it be possible to integrate the advantages of this block into the existing range or entry block, so we don't have multiple blocks that do _almost_ the same...

Builds, install, works fine. We do have a number of qtgui widgets that are Python-only, so that's only a minor point. Since the range block is also Python-only, I think...

The idea above was that this would be done externally with msg-to-var. A msg port would be cleaner, though.

@chrisjohgorman Are the summary and "steps to reproduce" describing the same problem?

Yes, you can open a PR, and request review by gmeyerho and mbr0wn.

My preference would be if it was always the user's preference, and not included in the yaml.

@chrisjohgorman I think this was fixed in #7207, which has been backported to 3.10 after the 3.10.10.0 release. Could you see if that addresses the problem?

I take it back. This fix was before 3.10.10.0.