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/2011-April/110854.html below:

Pure Python/C Accelerator Module Compatibiilty Requirements

[Python-Dev] PEP 399: Pure Python/C Accelerator Module Compatibiilty Requirements [Python-Dev] PEP 399: Pure Python/C Accelerator Module Compatibiilty RequirementsR. David Murray rdmurray at bitdance.com
Mon Apr 18 19:30:56 CEST 2011
On Mon, 18 Apr 2011 18:34:06 +0200, =?UTF-8?Q?=C3=89ric_Araujo?= <merwok at netwok.org> wrote:
> > Perhaps we need a @python_implementation_detail skip decorator?
>  That’s called test.support.cpython_only (see also 
>  test.support.check_impl_detail).  You’re welcome.

Nope.  That's not what I was talking about.  I was talking about marking
a test as something that we require only the *python* implementation of
a module to pass (presumably because it tests an internal implementation
detail).  Thus a C accelerator would not be expected to pass that
test, nor would a C# accelerator, but pypy or any platform without
an accelerator (that is, anything *using* the python code) would be
expected to pass it.

I would hope that such tests would be vanishingly rare (that is,
that all needed tests can be expressed as black box tests).

--
R. David Murray           http://www.bitdance.com
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