GITHUB . COM {}

Matching Content Categories {📚}

• Technology & Computing
• Mobile Technology & AI
• Transportation

Content Management System {📝}

What CMS is github.com built with?

Github.com is powered by 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 {🔍}

deprecatedcall, futurewarning, ronnypfannschmidt, warnings, deprecated, sign, add, issue, expected, def, pass, code, projects, closed, features, future, function, commented, member, navigation, solutions, pytest, pull, requests, actions, security, chrimaho, deprecationwarning, warning, pydeprecate, test, successfully, behaviour, import, deprecatedfunc, warnthis, futuredeprecationfunc, thecompiler, python, docs, missed, alias, marking, experimental, nicoddemus, github, labels, type, milestone, footer,

Topics {✒️}

marking experimental code activity chrimaho mentioned comment metadata assignees add futurewarning alternative solutions type projects projects milestone python docs warnings import warn implementing deprecated features compiler commented nicoddemus closed code def test_futures handle futurewarning aka marking pytest pass successfully test successfully current behaviour test cases additional context base class end users emphasis mine perfectly reasonable assigned labels labels type milestone relationships deprecated features regularly expected pendingdeprecationwarning warnings default warning expected behaviour github futurewarning verified 8062743 sign deprecated_func pass deprecated_call `deprecated_call future_deprecation_func features experimental deprecated warning warnings warn expected python

Payment Methods {📊}

• Braintree

Questions {❓}

• Already have an account?
• What's the problem this feature will solve?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:Add `FutureWarning` to `deprecated_call()`
      articleBody:#### What's the problem this feature will solve? When implementing deprecated features, we are regularly expected to use the [`DeprecationWarning`][DeprecationWarning] and [`PendingDeprecationWarning`][PendingDeprecationWarning] warnings. However, there is another one: [`FutureWarning`][FutureWarning]. This particular warning is used by packages such as [`pydeprecate`][pydeprecate] as the default warning for any functions that will be removed in the future. However, when I write a function that raises the [`FutureWarning`][FutureWarning] (or use the [`@deprecated`][pydeprecate] decorator), then [`deprecated_call()`][deprecated_call] currently does not catch the test successfully. #### Describe the solution you'd like I'd like to add [`FutureWarning`][FutureWarning] to the list of warnings which are captured by [`deprecated_call()`][deprecated_call]. This is the current behaviour: ```py from warnings import warn from pytest import deprecated_call def deprecated_func(): warn("This function is deprecated", DeprecationWarning) pass def future_deprecation_func(): warn("This function will be deprecated in the future", FutureWarning) pass def test_deprecated(): """Expected to pass""" with deprecated_call(): deprecated_func() def test_futures(): """Expected to fail""" with deprecated_call(): future_deprecation_func() ``` The expected behaviour would be for both of these two test cases to pass successfully. #### Alternative Solutions N/A #### Additional context N/A [DeprecationWarning]: https://docs.python.org/3/library/exceptions.html#DeprecationWarning [PendingDeprecationWarning]: https://docs.python.org/3/library/exceptions.html#PendingDeprecationWarning [FutureWarning]: https://docs.python.org/3/library/exceptions.html#FutureWarning [pydeprecate]: https://borda.github.io/pyDeprecate/ [deprecated_call]: https://docs.pytest.org/en/7.4.x/reference/reference.html#pytest.deprecated_call
      author:
         url:https://github.com/chrimaho
         type:Person
         name:chrimaho
      datePublished:2023-09-18T01:06:00.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:3
      url:https://github.com/11447/pytest/issues/11447
      context:https://schema.org
      headline:Add `FutureWarning` to `deprecated_call()`
      articleBody:#### What's the problem this feature will solve? When implementing deprecated features, we are regularly expected to use the [`DeprecationWarning`][DeprecationWarning] and [`PendingDeprecationWarning`][PendingDeprecationWarning] warnings. However, there is another one: [`FutureWarning`][FutureWarning]. This particular warning is used by packages such as [`pydeprecate`][pydeprecate] as the default warning for any functions that will be removed in the future. However, when I write a function that raises the [`FutureWarning`][FutureWarning] (or use the [`@deprecated`][pydeprecate] decorator), then [`deprecated_call()`][deprecated_call] currently does not catch the test successfully. #### Describe the solution you'd like I'd like to add [`FutureWarning`][FutureWarning] to the list of warnings which are captured by [`deprecated_call()`][deprecated_call]. This is the current behaviour: ```py from warnings import warn from pytest import deprecated_call def deprecated_func(): warn("This function is deprecated", DeprecationWarning) pass def future_deprecation_func(): warn("This function will be deprecated in the future", FutureWarning) pass def test_deprecated(): """Expected to pass""" with deprecated_call(): deprecated_func() def test_futures(): """Expected to fail""" with deprecated_call(): future_deprecation_func() ``` The expected behaviour would be for both of these two test cases to pass successfully. #### Alternative Solutions N/A #### Additional context N/A [DeprecationWarning]: https://docs.python.org/3/library/exceptions.html#DeprecationWarning [PendingDeprecationWarning]: https://docs.python.org/3/library/exceptions.html#PendingDeprecationWarning [FutureWarning]: https://docs.python.org/3/library/exceptions.html#FutureWarning [pydeprecate]: https://borda.github.io/pyDeprecate/ [deprecated_call]: https://docs.pytest.org/en/7.4.x/reference/reference.html#pytest.deprecated_call
      author:
         url:https://github.com/chrimaho
         type:Person
         name:chrimaho
      datePublished:2023-09-18T01:06:00.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:3
      url:https://github.com/11447/pytest/issues/11447
Person:
      url:https://github.com/chrimaho
      name:chrimaho
      url:https://github.com/chrimaho
      name:chrimaho
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:3
      interactionType:https://schema.org/CommentAction
      userInteractionCount:3

External Links {🔗}(7)

• How much profit is https://github.blog making per month?
• How much revenue does https://docs.python.org/3/library/exceptions.html#DeprecationWarning generate?
• Discover the revenue of https://docs.python.org/3/library/exceptions.html#PendingDeprecationWarning
• What are the total earnings of https://docs.python.org/3/library/exceptions.html#FutureWarning?
• How much cash flow does https://borda.github.io/pyDeprecate/ have monthly?
• What is the earnings of https://docs.pytest.org/en/7.4.x/reference/reference.html#pytest.deprecated_call?
• Get to know https://www.githubstatus.com/'s earnings

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