Practically speaking, since the jury is composed of multiple individuals, they're set up to express their "findings" via a strictly parameterized form where they check boxes or give numerical inputs.
In its more colloquial sense, I can see why you prefer to call that "answering" questions rather than "finding" facts.
However, it's silly to quibble over the parent thread's author's usage of "found" when it's the dominant phrasing used in the legal system.
Everything Everywhere All at Once was the last time I sat in a theater where, for the first half at least, I thought I was watching an instant classic.
But that movie just dragged on, and now I look back and see it as a bungled opportunity. It could've been so much tighter in the edit. They could've cut a third of the movie and made the whole thing so much better.
Playing devil's advocate: why assume Iraq would (attempt to) store VX in the same way? It actually has a thin ring of plausibility around it in the same the way you sometimes hear stories that Kim Jong Il would watch American movies and demand "I want us to build that".
"Circumstantial" evidence is often stronger than "direct" evidence. e.g. DNA is almost always "circumstantial", yet more modernly maligned eye witness evidence is "direct".
I just tried it and at least the autocomplete in IPython appears to ignore __all__ when suggesting possible imports. I haven't tried any other tools' autocompletes.
If module A has a small intended public API, you can structure it no matter how you want to achieve that. You can put those internal symbols behind their own object/class/module if you prefer.
Using `__all__` has one functional consequence, which is `from A import *`. Again, I would avoid * imports entirely, but if you want to try to curb possible downstream problems from users who do indeed use * imports, I would also prefer not defining `__all__` because it's extra boilerplate you have to maintain and can very easily be missed on future updates.
And please, just don't use * imports. It really doesn't save you much time at the cost of implicit untraceable behavior. If you don't worry about * imports, you don't need to add the __all__ boilerplate to every module.
This article is more about advertising a package called tach, that I suppose tries to add "true" private classes to Python.
But it doesn't actually enforce anything, because you still need to run their tool that checks anything. You could just easily configure your standard linter to enforce this type of thing rather than use a super specialized tool.
In its more colloquial sense, I can see why you prefer to call that "answering" questions rather than "finding" facts.
However, it's silly to quibble over the parent thread's author's usage of "found" when it's the dominant phrasing used in the legal system.