GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
OutcomeException should not be a subclass of Exception · Issue #580 · pytest-dev/pytest
Description:
Originally reported by: BitBucket: thiefmaster, GitHub: thiefmaster Imagine this code: def blackbox(callback, arg): # this is assumed to be application code try: callback(arg) except Exception: pass def test_callback(): def cb(x): if not...
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 employs 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 {💳}
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 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 {🔍}
code, exception, pytestbot, github, commented, ronnypfannschmidt, sign, issue, bitbucket, thiefmaster, application, type, projects, def, pass, pytestfail, email, comment, flub, bug, milestone, member, modified, milestones, thecompiler, navigation, pytest, pull, requests, actions, security, outcomeexception, subclass, closed, blackboxcb, testcase, dont, prevent, failure, test, fail, called, contributor, author, original, protect, added, problem, addressed, nicoddemus,
Topics {✒️}
org/pytest-dev/pytest/issue/580 activity personal information outcomeexception comment metadata assignees assigned labels type projects milestone 4 type projects compiler commented email sending failure major issue ronnypfannschmidt modified call pytest test runner compiler modified addressed type user code application code failed raised pytest testcase failure library function monkeypatch smtplib email unexpectedly exception block breaking things monkeypatched method floris bruynooghe bare exception 0 closed 100% complete relationships def blackbox def cb bug problem protect agains thiefmaster imagine milestone code fail called flub github exception email application pass bug testcase called protect blackbox cb thiefmaster
Payment Methods {📊}
- Braintree
Questions {❓}
- Already have an account?
Schema {🗺️}
DiscussionForumPosting:
context:https://schema.org
headline:OutcomeException should not be a subclass of Exception
articleBody:Originally reported by: **BitBucket: [thiefmaster](http://bitbucket.org/thiefmaster), GitHub: [thiefmaster](http://github.com/thiefmaster)**
---
Imagine this code:
```
def blackbox(callback, arg):
# this is assumed to be application code
try:
callback(arg)
except Exception:
pass
def test_callback():
def cb(x):
if not x:
import pytest
pytest.fail('foo')
blackbox(cb, True)
blackbox(cb, False)
```
The testcase will pass since `except Exception` will catch the `Failed` raised by `pytest.fail`. However, I don't think there is _any_ valid use-case for application code to prevent a testcase failure from propagating to the test runner.
A more practical example where this is a major issue is monkeypatching a library function to fail when called. For example, one might want to monkeypatch `smtplib.SMTP.connect` to fail when code tries to send an email unexpectedly - but chances are good that the application is wrapping that code in a `try...except Exception` block to prevent an email sending failure from breaking things (e.g. because the email is not very important). So now the `pytest.fail` called in the monkeypatched method will never propagate since it's caught by application code.
---
- Bitbucket: https://bitbucket.org/pytest-dev/pytest/issue/580
author:
url:https://github.com/pytestbot
type:Person
name:pytestbot
datePublished:2014-09-04T13:23:25.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:6
url:https://github.com/580/pytest/issues/580
context:https://schema.org
headline:OutcomeException should not be a subclass of Exception
articleBody:Originally reported by: **BitBucket: [thiefmaster](http://bitbucket.org/thiefmaster), GitHub: [thiefmaster](http://github.com/thiefmaster)**
---
Imagine this code:
```
def blackbox(callback, arg):
# this is assumed to be application code
try:
callback(arg)
except Exception:
pass
def test_callback():
def cb(x):
if not x:
import pytest
pytest.fail('foo')
blackbox(cb, True)
blackbox(cb, False)
```
The testcase will pass since `except Exception` will catch the `Failed` raised by `pytest.fail`. However, I don't think there is _any_ valid use-case for application code to prevent a testcase failure from propagating to the test runner.
A more practical example where this is a major issue is monkeypatching a library function to fail when called. For example, one might want to monkeypatch `smtplib.SMTP.connect` to fail when code tries to send an email unexpectedly - but chances are good that the application is wrapping that code in a `try...except Exception` block to prevent an email sending failure from breaking things (e.g. because the email is not very important). So now the `pytest.fail` called in the monkeypatched method will never propagate since it's caught by application code.
---
- Bitbucket: https://bitbucket.org/pytest-dev/pytest/issue/580
author:
url:https://github.com/pytestbot
type:Person
name:pytestbot
datePublished:2014-09-04T13:23:25.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:6
url:https://github.com/580/pytest/issues/580
Person:
url:https://github.com/pytestbot
name:pytestbot
url:https://github.com/pytestbot
name:pytestbot
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:6
interactionType:https://schema.org/CommentAction
userInteractionCount:6
External Links {🔗}(5)
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