1 new commit in pytest:
https://bitbucket.org/pytest-dev/pytest/commits/27b5ea7b6f5a/
Changeset: 27b5ea7b6f5a
Branch: yield-experimental-docs
User: nicoddemus
Date: 2015-04-03 22:44:06+00:00
Summary: Brought back discussion session
Reworded it a bit to bring it to par with the current status
Affected #: 1 file
diff -r 7663e5239695259c526f0a54c6e4fe22d200e7ec -r
27b5ea7b6f5a4466c356fa13ee49d0f944ca76e8 doc/en/yieldfixture.txt
--- a/doc/en/yieldfixture.txt
+++ b/doc/en/yieldfixture.txt
@@ -78,3 +78,23 @@
This behaviour makes sense if you consider that many different
test functions might use a module or session scoped fixture.
+
+Discussion and future considerations / feedback
+++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+There are some topics that are worth mentioning:
+
+- 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
+ multiple values as an alternative to current parametrization.
+ For now, you can just use the normal
+ :ref:`fixture parametrization <fixture-parametrize>`
+ mechanisms together with ``yield``-style fixtures.
+
+- lastly ``yield`` introduces more than one way to write
+ fixture functions, so what's the obvious way to a newcomer?
+
+If you want to feedback or participate in discussion of the above
+topics, please join our :ref:`contact channels`, you are most welcome.
Repository URL: https://bitbucket.org/pytest-dev/pytest/
--
This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.
_______________________________________________
pytest-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pytest-commit
