GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
Suggestion: merge .fixture and .yield_fixture · Issue #1461 · pytest-dev/pytest
Description:
The yield_fixture page says: lastly yield introduces more than one way to write fixture functions, so what’s the obvious way to a newcomer? My suggestion is to merge pytest.fixture and pytest.yield_fixture. Before: @pytest.fixture def fo...
Website Age:
17 years and 8 months (reg. 2007-10-09).
Matching Content Categories {📚}
- Technology & Computing
- Mobile Technology & AI
- Social Networks
Content Management System {📝}
What CMS is github.com built with?
Github.com utilizes WORDPRESS.
Traffic Estimate {📈}
What is the average monthly size of github.com audience?
🚀🌠 Tremendous Traffic: 10M - 20M visitors per month
Based on our best estimate, this website will receive around 10,653,731 visitors per month in the current month.
check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush
How Does Github.com Make Money? {💸}
Subscription Packages {💳}
We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.How Much Does Github.com Make? {💰}
Subscription Packages {💳}
Prices on github.com are in US Dollars ($).
They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 5,316,083 paying customers.
The estimated monthly recurring revenue (MRR) is $22,327,549.
The estimated annual recurring revenues (ARR) are $267,930,588.
Wordpress Themes and Plugins {🎨}
What WordPress theme does this site use?
It is strange but we were not able to detect any theme on the page.
What WordPress plugins does this website use?
It is strange but we were not able to detect any plugins on the page.
Keywords {🔍}
fixture, nicoddemus, pytest, yieldfixture, yield, commented, code, member, pytestfixture, def, requestaddfinalizer, sign, return, fixtures, type, proposal, feature, update, pull, requests, projects, suggestion, merge, issue, closed, csaftoiu, function, finalization, teardown, smtp, work, decide, deprecate, warning, system, github, content, navigation, open, source, issues, actions, security, newcomer, pytestyieldfixture, foo, bar, boof, somestuff, morestuff,
Topics {✒️}
/notifications/unsubscribe/aacoau59mp9hg4uoywbflsapvkq2_t-oks5qmszmgajpzm4h0eou backward compatibility issues perform finalization code personal information suggestion pytest supports execution stackoverflow question today pyup-bot mentioned assigned labels type callback-teardown method comment metadata assignees yield_fixture def boof write fixture functions lastly yield introduces type projects fixture def foo fixture def boof projects milestone compiler commented compiler member code depending fixture function returns smtp = smtplib pytest trainings finished executing suggest deprecating idiomatic python suggestion normal fixtures merge pytest def smtp code finished execution feature type simply return return-style yield_fixture page integrate yield_fixture teardown smtp documentation section yieldwill execute straightforward change function object official/recommended long run main point remove support future version separate concerns proposal proposal gather opinions
Payment Methods {📊}
- Braintree
Questions {❓}
- Already have an account?
- I've always thought the same, but I thought there was some obscure reason it was done the way it is rather than combining them since the beginning - seems like I'm wrong?
- The reason?
- Lastly yield introduces more than one way to write fixture functions, so what’s the obvious way to a newcomer?
Schema {🗺️}
DiscussionForumPosting:
context:https://schema.org
headline:Suggestion: merge .fixture and .yield_fixture
articleBody:The [yield_fixture](https://pytest.org/latest/yieldfixture.html) page says:
> lastly yield introduces more than one way to write fixture functions, so what’s the obvious way to a newcomer?
My suggestion is to merge `pytest.fixture` and `pytest.yield_fixture`.
Before:
```
@pytest.fixture
def foo():
return ['bar']
@pytest.yield_fixture
def boof():
with some_stuff as more_stuff:
yield even_more_stuff(more_stuff)
```
After:
```
@pytest.fixture
def foo():
return ['bar']
@pytest.fixture
def boof():
with some_stuff as more_stuff:
yield even_more_stuff(more_stuff)
```
This should be possible - if calling the fixture function returns a generator, then do what `yield_fixture` currently does, otherwise (i.e. if it returns a value), then do what `fixture` currently does.
The reason? There will be one less choice for a newcomer to make - which decorator to call.
---
Further, the documentation section "Fixture finalization / executing teardown code" can now read something like this:
> pytest supports execution of fixture specific finalization code when the fixture goes out of scope. By yielding the fixture object instead of returning it, you can perform finalization code after the test has finished executing:
```
# content of conftest.py
import smtplib
import pytest
@pytest.fixture(scope="module")
def smtp(request):
smtp = smtplib.SMTP("smtp.gmail.com")
yield smtp # provide the fixture value
print("teardown smtp")
smtp.close()
```
> The code after the `yield`will execute when the last test using the fixture in the module has finished execution.
This is a straightforward change, syntactically (`return` -> `yield`), even if the internals are quite different, and is intuitive enough to me, and I suspect anyone who gets how generators work.
I suggest deprecating the old callback-teardown method since the `yield` mechanism is superior in every way. Really it should be the only way, but it may be confusing to someone who expects to be able to simply return a value, and so returning a value will just work as well.
author:
url:https://github.com/csaftoiu
type:Person
name:csaftoiu
datePublished:2016-03-18T17:29:41.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:8
url:https://github.com/1461/pytest/issues/1461
context:https://schema.org
headline:Suggestion: merge .fixture and .yield_fixture
articleBody:The [yield_fixture](https://pytest.org/latest/yieldfixture.html) page says:
> lastly yield introduces more than one way to write fixture functions, so what’s the obvious way to a newcomer?
My suggestion is to merge `pytest.fixture` and `pytest.yield_fixture`.
Before:
```
@pytest.fixture
def foo():
return ['bar']
@pytest.yield_fixture
def boof():
with some_stuff as more_stuff:
yield even_more_stuff(more_stuff)
```
After:
```
@pytest.fixture
def foo():
return ['bar']
@pytest.fixture
def boof():
with some_stuff as more_stuff:
yield even_more_stuff(more_stuff)
```
This should be possible - if calling the fixture function returns a generator, then do what `yield_fixture` currently does, otherwise (i.e. if it returns a value), then do what `fixture` currently does.
The reason? There will be one less choice for a newcomer to make - which decorator to call.
---
Further, the documentation section "Fixture finalization / executing teardown code" can now read something like this:
> pytest supports execution of fixture specific finalization code when the fixture goes out of scope. By yielding the fixture object instead of returning it, you can perform finalization code after the test has finished executing:
```
# content of conftest.py
import smtplib
import pytest
@pytest.fixture(scope="module")
def smtp(request):
smtp = smtplib.SMTP("smtp.gmail.com")
yield smtp # provide the fixture value
print("teardown smtp")
smtp.close()
```
> The code after the `yield`will execute when the last test using the fixture in the module has finished execution.
This is a straightforward change, syntactically (`return` -> `yield`), even if the internals are quite different, and is intuitive enough to me, and I suspect anyone who gets how generators work.
I suggest deprecating the old callback-teardown method since the `yield` mechanism is superior in every way. Really it should be the only way, but it may be confusing to someone who expects to be able to simply return a value, and so returning a value will just work as well.
author:
url:https://github.com/csaftoiu
type:Person
name:csaftoiu
datePublished:2016-03-18T17:29:41.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:8
url:https://github.com/1461/pytest/issues/1461
Person:
url:https://github.com/csaftoiu
name:csaftoiu
url:https://github.com/csaftoiu
name:csaftoiu
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:8
interactionType:https://schema.org/CommentAction
userInteractionCount:8
External Links {🔗}(4)
Analytics and Tracking {📊}
- Site Verification - Google
Libraries {📚}
- Clipboard.js
- D3.js
- Lodash
Emails and Hosting {✉️}
Mail Servers:
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
Name Servers:
- dns1.p08.nsone.net
- dns2.p08.nsone.net
- dns3.p08.nsone.net
- dns4.p08.nsone.net
- ns-1283.awsdns-32.org
- ns-1707.awsdns-21.co.uk
- ns-421.awsdns-52.com
- ns-520.awsdns-01.net