4 ms·
I only rarely delve into the python world, but as a .net developer I always found it odd and confusing that the error message comes after the stack trace in pyt
by e-master 4y ago
I only rarely delve into the python world, but as a .net developer I always found it odd and confusing that the error message comes after the stack trace in python. I don’t see people complaining about it, so maybe it’s just a matter of habit?
- kzrdude 4y agoI guess it's just a habit even if I think it's mildly confusing too. But: it's kind of a virtue that the most important error message comes last. Far too many (ahead of time) compilers output too many errors. The most likely error to matter is the first one, but it is often scrolled way off screen; the following errors might even just be side effects that mislead or confuse the new users.
- AdamN 4y agoOn the CLI, you'll see the error just above the prompt and then the stack trace above that. It makes sense since the user is always reading up the terminal in reverse order.