mwchase

I was looking into this, and I think I found the issue. In the docparams extension, the `visit_return`, `visit_yield`, and `visit_raise` methods need an extra block after the ```python if...

Ah, I guess I should file a followup issue for `raises` and `yields`. I can try to get that together tomorrow, if nobody else gets there first.

After I thought about this overnight, it occurred to me that there might be a workaround. I'll see if it works later today; it might be possible to make this...

I was able to hack this together by using a text field in another cell to get input to a filtering operation to preprocess the table, and then put them...

Here's what I've got so far: ```python @app.cell def __(mo): filter_text = mo.ui.text() return filter_text, @app.cell def __(): table_entries = [] # Edit this to have something actually interesting in...

... Of course, it also works to skip making the `hstack` and just use the `label` argument to `text()`.

For what it's worth, multimetric or some other project should probably *replace* radon for the purpose of calculating Halstead metrics. Radon's Halstead calculations only count a subset of relevant operations,...

I can give an example of a file from one of my projects that radon measures as all zeros, despite the fact that there's definitely a bunch of stuff happening...