On May 10, 2020, at 14:33, Christopher Barker email@example.com wrote:
Having a "tabnanny-like" function / module in the stdlib would be nice, though I'd think a stand alone module in PyPi would be almost as good, and a good way to see if it gains traction.
Plus, it might well turn out that, say, the right thing for most Windows users and the right thing for most iOS Pythonista users is sufficiently different that two separate defancier packages are better than a one-size-fits-all could be, which we’d find out a lot more easily if people go out and use it in the field than if we try to design it here.
BTW -- there are a whole lot of Syntax Errors that a semi smart algorithm could provide meaningful suggestions about about. I'm pretty sure that's come up before on this list, but maybe "helpful" mode you could run Python in that would do that for all Syntax errors that it could. We could even have a way for folks to extend it with additional checks.
This already exists on PyPI. Actually, there are a few different ones.
One of them (I think friendly-tracebacks?) is very detailed. One of the authors sometimes posts about it here, when we’re talking about how some exception should be improved, with an example showing that they’ve already thought of it and done something better than is being proposed in the list.:)
That one may already be a category killer. I looked over some of the others and the only thing that jumped out at me was that one of them (better-errors?) integrates really nicely into iPython and Jupyter (using iPython’s syntax coloring settings, making more use of line-drawing and box characters, etc.)
But that doesn’t mean the category killer should be in the stdlib; I suspect they’re still improving it at a much faster pace than the stdlib could handle. But maybe the docs should link to it. The only problem is that the obvious places (like Interface Options section in the Usage docs) are things almost nobody reads…