On Mon, Dec 11, 2017 at 1:11 PM, Carl Friedrich Bolz wrote:
> we require and have always required app-level tests for every new
> feature up to the finer details. The CPython test suite is often not
> very thorough, and we often work under the assumption that if our own
> tests about a feature w
Hi Manuel,
we require and have always required app-level tests for every new
feature up to the finer details. The CPython test suite is often not
very thorough, and we often work under the assumption that if our own
tests about a feature work, the feature works.
The coding guide states that alrea
It's not clear if you're looking for input from the peanut gallery,
but here is my $0.02:
First test at the level of the feature as exposed to a user. This
makes sense to write before implementation starts, and is highly
unlikely to change if the implementation gets refactored. It sounds
like your
Hi,
I'm currently implementing PEP 526 [1], which requires additions to the
interpreter from the parser down to the bytecode interpreter. Since
this is a common task, I want to expand the documentation a bit, adding
a "how to extend the interpreter" recipe.
One thing which I wasn't 100% sur
