[issue45063] PEP 657 Fine Grained Error Locations: omit indicators if they are one the whole line, to make tracebacks shorter

2021-09-16 Thread STINNER Victor
STINNER Victor added the comment: It seems that I will have to learn to use PYTHONNODEBUGRANGES=1 and -Xno_debug_ranges. I close the issue. -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker

[issue45063] PEP 657 Fine Grained Error Locations: omit indicators if they are one the whole line, to make tracebacks shorter

2021-08-31 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: > Python 3.11 makes it worse: up to 1.5x longer Sound like you likely want to use the environment variable to deactivate the extra information ;) -- ___ Python tracker

[issue45063] PEP 657 Fine Grained Error Locations: omit indicators if they are one the whole line, to make tracebacks shorter

2021-08-31 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: >In my example, there are 6 frames. The indicators cover the whole line of 3 >frames: 50%. It's a common case, it's not special. Special is not uncommon, is just some different behaviour rather than the default one. I am not arguing that is a rare

[issue45063] PEP 657 Fine Grained Error Locations: omit indicators if they are one the whole line, to make tracebacks shorter

2021-08-31 Thread STINNER Victor
STINNER Victor added the comment: > I don't follow what you want to change in 3.10.0 final, PEP 657 is for Python > 3.11. Can you clarify? Ah, I thaught that the PEP was implemented in 3.10, I didn't notice that it's a new feature of Python 3.11 :-) > Regarding the issue: I understand what