Skip to content

yield_fixture docs need updating #690

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pytestbot opened this issue Feb 28, 2015 · 2 comments
Closed

yield_fixture docs need updating #690

pytestbot opened this issue Feb 28, 2015 · 2 comments
Labels
type: docs documentation improvement, missing or needing clarification type: enhancement new feature or API change, should be merged into features branch

Comments

@pytestbot
Copy link
Contributor

Originally reported by: Brianna Laugher (BitBucket: pfctdayelise, GitHub: pfctdayelise)


http://pytest.org/latest/yieldfixture.html says

“yielding” fixture values is an experimental feature and its exact declaration may change later but earliest in a 2.5 release. You can thus safely use this feature in the 2.4 series but may need to adapt later.

I think it is not actually the case that it is still experimental - it can cause confusion about if this feature should be used or not.

I am not sure what exactly the official status of it is now, so perhaps someone else can suggest what the wording should be.


@pytestbot
Copy link
Contributor Author

Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):


I guess you are right and we can strike the wording. If we change it now we need to think about backward-compatibility because it is in relatively wide use, independently from the warning. Feel free to do a PR.

@pytestbot
Copy link
Contributor Author

@pytestbot pytestbot added type: enhancement new feature or API change, should be merged into features branch type: docs documentation improvement, missing or needing clarification labels Jun 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: docs documentation improvement, missing or needing clarification type: enhancement new feature or API change, should be merged into features branch
Projects
None yet
Development

No branches or pull requests

1 participant