GITHUB . COM {}

Matching Content Categories {📚}

• DIY & Home Improvement
• Home & Garden
• Dating & Relationships

Content Management System {📝}

What CMS is github.com built with?

Github.com operates using 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,000,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Github.com Make Money? {💸}

Subscription Packages {💳}

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 4,989,889 paying customers.
The estimated monthly recurring revenue (MRR) is $20,957,532.
The estimated annual recurring revenues (ARR) are $251,490,385.

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 {🔍}

fixtures, fixturerequest, fixture, request, subrequest, bluetech, subclass, toprequest, abstract, proposal, bit, issue, add, sign, fixturerequestsubrequest, type, feature, pytest, projects, confusing, function, item, propose, renaming, change, directly, added, make, nicoddemus, navigation, pull, requests, actions, security, refactor, closed, opened, situation, test, parametrized, requestparam, internals, drive, holds, requesting, fix, subrequestfix, points, understand, initial,

Topics {✒️}

longer subclass fixturerequest/toprequest nicoddemus edits member 9e164fc bluetech closed add toprequest subclass found pytest-alembic 0e888ac bluetech mentioned comment metadata assignees involving fixtures directly personal information fixtures top fixturerequest form instantiate fixturerequest directly assigned labels topic disruptive breaking change official breaking change propose making fixturerequest leaving deprecated aliases type projects make fixturerequest abstract projects milestone refactor fixturerequest/subrequest fixturerequest/subrequest situation refactor `fixturerequest`/`subrequest` toprequest subclass test-function request bluetech added pytest internals pytest-yield pytest-wdl pytest-play subclass subrequest indirectly type fixtures needed test function propose introducing parametrized fixtures abstract class explicitly requested named requestfixture chain/stack pretty hard clarify things makes sense break plugins proposal proposal gather opinions feature type milestone relationships renaming fixturerequest subrequest inherits request inside

Payment Methods {📊}

• Braintree

Questions {❓}

• Already have an account?
• And SubRequest would no longer subclass FixtureRequest/TopRequest, just implement the abstract class?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:fixtures: refactor `FixtureRequest`/`SubRequest` a bit
      articleBody:The `FixtureRequest`/`SubRequest` situation is currently quite confusing. - `FixtureRequest` (on its own, not its subclass `SubRequest`) is used for the `request` fixture in a test function itself. One is created even if the `request` fixture is not explicitly requested. The name is a bit confusing -- it is not a request for a fixture. I think it wanted to be named `RequestFixture` i.e. the `request` fixture, but not 100% sure. A test function itself cannot be parametrized using `request.param`, only a fixture can. For `FixtureRequest` the `request.scope` is always `function` and the `request.node` is the item. In the pytest internals, it is used to drive getting the fixture values of the fixtures needed by the item (`_fillfixtures`). - `SubRequest` is used for `request` inside a fixture. The `SubRequest` holds a reference to the `FixtureDef` it handles. For parametrized fixtures it holds the parameter value (`request.param`). In the pytest internals, it is used to drive the execution of a specific "fixture request" . While executing an item, the `SubRequest`s and the top `FixtureRequest` form a chain/stack. For example, if we have `test_it` requesting `fix1` requesting `fix2`, then there is `SubRequest(fix2)` which points to `SubRequest(fix1)` which points to `FixtureRequest(test_it)`. This is only used in practice for printing a "fixture stack" in some errors, but is useful to understand conceptually. `SubRequest` inherits from `FixtureRequest`, but in a pretty hard to understand way, e.g. its `__init__` doesn't call the super. As an initial way to clarify things a bit, I propose making `FixtureRequest` itself abstract, and add a new `TopRequest` subclass for the test-function `request`. The name `TopRequest` would not be my TopChoice, but renaming `FixtureRequest` or `SubRequest` at this point would be a disruptive breaking change, so better to choose a name which makes sense in relation to `SubRequest`. This will break plugins which instantiate `FixtureRequest` directly. It's private so not an official breaking change. I found `pytest-alembic`, `pytest-yield`, `pytest-wdl`, `pytest-play`. I can notify them about this change if this proposal is accepted.
      author:
         url:https://github.com/bluetech
         type:Person
         name:bluetech
      datePublished:2023-07-16T20:44:11.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:2
      url:https://github.com/11218/pytest/issues/11218
      context:https://schema.org
      headline:fixtures: refactor `FixtureRequest`/`SubRequest` a bit
      articleBody:The `FixtureRequest`/`SubRequest` situation is currently quite confusing. - `FixtureRequest` (on its own, not its subclass `SubRequest`) is used for the `request` fixture in a test function itself. One is created even if the `request` fixture is not explicitly requested. The name is a bit confusing -- it is not a request for a fixture. I think it wanted to be named `RequestFixture` i.e. the `request` fixture, but not 100% sure. A test function itself cannot be parametrized using `request.param`, only a fixture can. For `FixtureRequest` the `request.scope` is always `function` and the `request.node` is the item. In the pytest internals, it is used to drive getting the fixture values of the fixtures needed by the item (`_fillfixtures`). - `SubRequest` is used for `request` inside a fixture. The `SubRequest` holds a reference to the `FixtureDef` it handles. For parametrized fixtures it holds the parameter value (`request.param`). In the pytest internals, it is used to drive the execution of a specific "fixture request" . While executing an item, the `SubRequest`s and the top `FixtureRequest` form a chain/stack. For example, if we have `test_it` requesting `fix1` requesting `fix2`, then there is `SubRequest(fix2)` which points to `SubRequest(fix1)` which points to `FixtureRequest(test_it)`. This is only used in practice for printing a "fixture stack" in some errors, but is useful to understand conceptually. `SubRequest` inherits from `FixtureRequest`, but in a pretty hard to understand way, e.g. its `__init__` doesn't call the super. As an initial way to clarify things a bit, I propose making `FixtureRequest` itself abstract, and add a new `TopRequest` subclass for the test-function `request`. The name `TopRequest` would not be my TopChoice, but renaming `FixtureRequest` or `SubRequest` at this point would be a disruptive breaking change, so better to choose a name which makes sense in relation to `SubRequest`. This will break plugins which instantiate `FixtureRequest` directly. It's private so not an official breaking change. I found `pytest-alembic`, `pytest-yield`, `pytest-wdl`, `pytest-play`. I can notify them about this change if this proposal is accepted.
      author:
         url:https://github.com/bluetech
         type:Person
         name:bluetech
      datePublished:2023-07-16T20:44:11.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:2
      url:https://github.com/11218/pytest/issues/11218
Person:
      url:https://github.com/bluetech
      name:bluetech
      url:https://github.com/bluetech
      name:bluetech
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:2
      interactionType:https://schema.org/CommentAction
      userInteractionCount:2

External Links {🔗}(2)

• Check the income stats for https://github.blog
• How much profit is https://www.githubstatus.com/ making per month?

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