From 9b9355b8da3a96843e9dfdbb92ea982c16e38aff Mon Sep 17 00:00:00 2001 From: holger krekel Date: Tue, 1 Oct 2013 14:30:53 +0200 Subject: [PATCH] fix typos (thanks @faassen) --- doc/en/yieldfixture.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/en/yieldfixture.txt b/doc/en/yieldfixture.txt index f2978b728..76ddbfaf7 100644 --- a/doc/en/yieldfixture.txt +++ b/doc/en/yieldfixture.txt @@ -8,7 +8,7 @@ Fixture functions using "yield" / context manager integration .. regendoc:wipe -pytest-2.4 allows fixture functions to seemlessly use a ``yield`` instead +pytest-2.4 allows fixture functions to seamlessly use a ``yield`` instead of a ``return`` statement to provide a fixture value while otherwise fully supporting all other fixture features. @@ -92,7 +92,7 @@ In general, the advantages of the using a ``yield`` fixture syntax are: However, there are also limitations or foreseeable irritations: -- usually ``yield`` is typically used for producing multiple values. +- usually ``yield`` is used for producing multiple values. But fixture functions can only yield exactly one value. Yielding a second fixture value will get you an error. It's possible we can evolve pytest to allow for producing