A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2015-June/140533.html below:

[Python-Dev] PEP 490: Chain exceptions at C level

[Python-Dev] PEP 490: Chain exceptions at C level [Python-Dev] PEP 490: Chain exceptions at C levelYury Selivanov yselivanov.ml at gmail.com
Sat Jun 20 21:29:47 CEST 2015
On 2015-06-20 3:16 PM, M.-A. Lemburg wrote:
> On 20.06.2015 09:30, Victor Stinner wrote:
>> >Hi,
>> >
>> >I didn't get much feedback on this PEP. Since the Python 3.6 branch is
>> >open (default), it's probably better to push such change in the
>> >beginning of the 3.6 cycle, to catch issues earlier.
>> >
>> >Are you ok to chain exceptions at C level by default?
> I think it's a good idea to make C APIs available to
> simplify chaining exceptions at the C level, but don't
> believe that always doing this by default is a good idea.
> It should really be a case-by-case decision, IMO.

Exactly my thoughts.

Maybe PyErr_SetStringChained, PyErr_FormatChained, etc
is better?

Yury
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4