GNU bug report logs -
#70653
[PATCH] Support source line location for Python ExceptionGroup
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Eli Zaretskii wrote:
>
> > From: ". shynur" <one.last.kiss <at> outlook.com>
> > Date: Mon, 29 Apr 2024 16:24:10 +0000
> > msip_labels:
> >
> > (This patch is written for Inferior Python mode.)
> >
> > The original behavior considered only the case of
> > single exception:
> >
> > ```
> > Traceback (most recent call last):
> > File "<string>", line 17, in __PYTHON_EL_eval
> > File "c:/Users/shynur/Desktop/Python/a.py", line 1, in <module>
> > raise Exception
> > Exception
> > ```
> >
> > In the above example, one can click at the 3rd line to jump
> > to the corresponding source line. This patch adds support
> > for the following case (i.e., the built-in ExceptionGroup):
> >
> > ```
> > + Exception Group Traceback (most recent call last):
> > | File "<string>", line 17, in __PYTHON_EL_eval
> > | File "c:/Users/shynur/Desktop/Python/a.py", line 1, in <module>
> > | raise ExceptionGroup("", [Exception()])
> > | ExceptionGroup: (1 sub-exception)
> > +-+---------------- 1 ----------------
> > | Exception
> > +------------------------------------
> > ```
>
> Adding kobarity to the discussion.
It looks good to me. Is it better to write NEWS since it is a change
of the customize variable?
Maybe we should also add ExceptionGroup as a Python keyword. The
patch is attached. Should I open a new bug?
[0001-Add-ExceptionGroup-as-a-Python-keyword.patch (application/octet-stream, attachment)]
This bug report was last modified 1 year and 54 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.