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

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

[Patches] PyObject_GetAttr/PyObject_SetAttr core dumps if given non-string names)

• Previous message: [Python-Dev] testing the Python/C API (was: Re: [Patches] PyObject_GetAttr/PyObject_SetAttr core dumps if given non-string names)
• Next message: [Python-Dev] Re: testing the Python/C API (was: Re: [Patches] PyObject_GetAttr/PyObject_SetAttr core dumps if given non-string names)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I think testing the C API directly is a great idea!  Sorry I missed it
the first time around.

I don't think I understand the suggested approach well enough to
critique it.  Most of the tests need to be written in C, right?  When
an error is encountered, it seems that you should check what the C API
returns *and* what happens at the Python level, i.e. whether the call
sets a Python exception (or clears an existing Python exception).

I guess you ought to show us the code.  I don't think it will go in
Python 1.6, but it sounds like a valuable component for future
releases. 

Jeremy

• Previous message: [Python-Dev] testing the Python/C API (was: Re: [Patches] PyObject_GetAttr/PyObject_SetAttr core dumps if given non-string names)
• Next message: [Python-Dev] Re: testing the Python/C API (was: Re: [Patches] PyObject_GetAttr/PyObject_SetAttr core dumps if given non-string names)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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