
GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
Doctests on properties do not detect line numbers Β· Issue #6082 Β· pytest-dev/pytest
Description:
When there are doctest tests on a @property method, pytest does not show the line number where the error occurred. For example on code class Fun(object): @property def test_prop(self): ''&#...
Website Age:
17 years and 8 months (reg. 2007-10-09).
Matching Content Categories {π}
- Technology & Computing
- Personal Finance
- Graphic Design
Content Management System {π}
What CMS is github.com built with?
Github.com relies on 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 {π}
pytest, doctests, merge, verified, issue, line, kondratyevnv, python, sign, properties, output, added, plugin, related, type, code, projects, doctest, tests, funtestprop, thing, expected, mentioned, bors, commits, reference, navigation, open, pull, requests, actions, security, detect, numbers, closed, property, number, test, hypothesis, item, dont, builtin, topic, reporting, terminal, userfacing, messages, errors, bug, problem,
Topics {βοΈ}
assigned labels plugin personal information doctests fix line detection user-facing messages comment metadata assignees type projects projects milestone doctest tests open doctests related line number code addressed type hypothesis/examples' pytest pytest-5 pytest doctest python 3 python 2 error occurred test_prop _________________________ location unknown test_prop expected expected output reporting related terminal output bug problem doctests errors type milestone relationships github tests hypothesis-4 properties fun thing' skip jump sign show object 5rc1 py-1 pluggy-0 rootdir py showing 17rc1 results
Payment Methods {π}
- Braintree
Questions {β}
- Already have an account?
- Notice ?
Schema {πΊοΈ}
DiscussionForumPosting:
context:https://schema.org
headline:Doctests on properties do not detect line numbers
articleBody:<!--
Thanks for submitting an issue!
Here's a quick checklist for what to provide:
-->
When there are doctest tests on a `@property` method, pytest does not show the line number where the error occurred. For example on code
```python
class Fun(object):
@property
def test_prop(self):
'''
>>> Fun().test_prop
'another thing'
'''
return 'something'
```
running pytest produces the following output
```
python3 -m pytest --doctest-modules
============================= test session starts ==============================
platform linux -- Python 3.7.5rc1, pytest-5.2.2, py-1.8.0, pluggy-0.12.0
hypothesis profile 'default' -> database=DirectoryBasedExampleDatabase('/<some-path>/.hypothesis/examples')
rootdir: /<some-path>
plugins: hypothesis-4.41.3
collected 1 item
hello.py F [100%]
=================================== FAILURES ===================================
________________________ [doctest] hello.Fun.test_prop _________________________
EXAMPLE LOCATION UNKNOWN, not showing all tests of that example
??? >>> Fun().test_prop
Expected:
'another thing'
Got:
'something'
/<some-path>/hello.py:None: DocTestFailure
============================== 1 failed in 0.01s ===============================
```
Notice `???` instead of the line number. Expected output would be
```
005
006 >>> Fun().test_prop
Expected:
'another thing'
Got:
'something'
```
I've tried it with Python 3.7.5rc1, Python 3.8.0, and Python 2.7.17rc1. The results are the same.
author:
url:https://github.com/kondratyev-nv
type:Person
name:kondratyev-nv
datePublished:2019-10-27T14:40:44.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:1
url:https://github.com/6082/pytest/issues/6082
context:https://schema.org
headline:Doctests on properties do not detect line numbers
articleBody:<!--
Thanks for submitting an issue!
Here's a quick checklist for what to provide:
-->
When there are doctest tests on a `@property` method, pytest does not show the line number where the error occurred. For example on code
```python
class Fun(object):
@property
def test_prop(self):
'''
>>> Fun().test_prop
'another thing'
'''
return 'something'
```
running pytest produces the following output
```
python3 -m pytest --doctest-modules
============================= test session starts ==============================
platform linux -- Python 3.7.5rc1, pytest-5.2.2, py-1.8.0, pluggy-0.12.0
hypothesis profile 'default' -> database=DirectoryBasedExampleDatabase('/<some-path>/.hypothesis/examples')
rootdir: /<some-path>
plugins: hypothesis-4.41.3
collected 1 item
hello.py F [100%]
=================================== FAILURES ===================================
________________________ [doctest] hello.Fun.test_prop _________________________
EXAMPLE LOCATION UNKNOWN, not showing all tests of that example
??? >>> Fun().test_prop
Expected:
'another thing'
Got:
'something'
/<some-path>/hello.py:None: DocTestFailure
============================== 1 failed in 0.01s ===============================
```
Notice `???` instead of the line number. Expected output would be
```
005
006 >>> Fun().test_prop
Expected:
'another thing'
Got:
'something'
```
I've tried it with Python 3.7.5rc1, Python 3.8.0, and Python 2.7.17rc1. The results are the same.
author:
url:https://github.com/kondratyev-nv
type:Person
name:kondratyev-nv
datePublished:2019-10-27T14:40:44.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:1
url:https://github.com/6082/pytest/issues/6082
Person:
url:https://github.com/kondratyev-nv
name:kondratyev-nv
url:https://github.com/kondratyev-nv
name:kondratyev-nv
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:1
interactionType:https://schema.org/CommentAction
userInteractionCount:1
External Links {π}(2)
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