GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
rewrite does not work automatically for plugins in develop mode · Issue #1934 · pytest-dev/pytest
Description:
pytest-mock uses pytest's assert introspection to enrich the error message when one of the standard mock.assert* methods fail. Those asserts are in the plugin module (pytest_mock.py), and while...
Website Age:
17 years and 9 months (reg. 2007-10-09).
Matching Content Categories {📚}
- Mobile Technology & AI
- Social Networks
- Careers
Content Management System {📝}
What CMS is github.com built with?
Github.com is built with 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 5,013,426 paying customers.
The estimated monthly recurring revenue (MRR) is $21,056,387.
The estimated annual recurring revenues (ARR) are $252,676,649.
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, mode, update, development, issue, nicoddemus, plugins, ronnypfannschmidt, sign, metadata, rewriting, pull, requests, projects, rewrite, work, develop, rewritten, assertion, mentioned, commented, member, navigation, pytestdev, code, actions, security, automatically, closed, assert, plugin, module, installed, function, entrypointdistgetmetadatarecord, egg, sourcestxt, record, added, commit, references, fixed, github, labels, type, milestone, footer, skip, content, menu,
Topics {✒️}
04cf5e1 nicoddemus mentioned personal information rewrite fixed assertion rewriting nicoddemus mentioned ronnypfannschmidt closed egg meta-data standard mock assert methods fail access egg metadata time assert rewriting comment metadata assignees nicoddemus added type projects projects milestone update tests code pytest' assertion rewriting development mode rewrite py develop assert introspection txt metadata error message python setup rewrite_hook = hook empty list makes sense call register_assert_rewrite big deal fix/workaround general tool assigned labels labels type milestone relationships work automatically function _consider_importhook fn = entry github plugin module installed plugins development rewritten work installed entry function module txt plugin
Payment Methods {📊}
- Braintree
Questions {❓}
- Already have an account?
- Any other ideas on how to fix/workaround it?
- Txt then?
Schema {🗺️}
DiscussionForumPosting:
context:https://schema.org
headline:rewrite does not work automatically for plugins in develop mode
articleBody:`pytest-mock` uses pytest's assert introspection to enrich the error message when one of the standard `mock.assert*` methods fail. Those asserts are in the plugin module (`pytest_mock.py`), and while they are rewritten just fine when installed from a package, they don't get rewritten in development mode (`python setup.py develop`).
I tracked down the problem to our code which tries to rewrite all modules of installed plugins in `config.py`, function `_consider_importhook`:
``` python
self.pluginmanager.rewrite_hook = hook
for entrypoint in pkg_resources.iter_entry_points('pytest11'):
for entry in entrypoint.dist._get_metadata('RECORD'):
fn = entry.split(',')[0]
...
```
When in development mode, `entrypoint.dist._get_metadata('RECORD')` returns an empty list; digging into that method I noticed it tries to access EGG metadata. Being in development mode, there's no EGG meta-data, so it makes sense.
I think the only solution is to move the function which needs assertion rewriting to its own "util" module and call `register_assert_rewrite` before importing it (which is no big deal).
Any other ideas on how to fix/workaround it?
cc @flub
author:
url:https://github.com/nicoddemus
type:Person
name:nicoddemus
datePublished:2016-09-15T00:18:28.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:3
url:https://github.com/1934/pytest/issues/1934
context:https://schema.org
headline:rewrite does not work automatically for plugins in develop mode
articleBody:`pytest-mock` uses pytest's assert introspection to enrich the error message when one of the standard `mock.assert*` methods fail. Those asserts are in the plugin module (`pytest_mock.py`), and while they are rewritten just fine when installed from a package, they don't get rewritten in development mode (`python setup.py develop`).
I tracked down the problem to our code which tries to rewrite all modules of installed plugins in `config.py`, function `_consider_importhook`:
``` python
self.pluginmanager.rewrite_hook = hook
for entrypoint in pkg_resources.iter_entry_points('pytest11'):
for entry in entrypoint.dist._get_metadata('RECORD'):
fn = entry.split(',')[0]
...
```
When in development mode, `entrypoint.dist._get_metadata('RECORD')` returns an empty list; digging into that method I noticed it tries to access EGG metadata. Being in development mode, there's no EGG meta-data, so it makes sense.
I think the only solution is to move the function which needs assertion rewriting to its own "util" module and call `register_assert_rewrite` before importing it (which is no big deal).
Any other ideas on how to fix/workaround it?
cc @flub
author:
url:https://github.com/nicoddemus
type:Person
name:nicoddemus
datePublished:2016-09-15T00:18:28.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:3
url:https://github.com/1934/pytest/issues/1934
Person:
url:https://github.com/nicoddemus
name:nicoddemus
url:https://github.com/nicoddemus
name:nicoddemus
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:3
interactionType:https://schema.org/CommentAction
userInteractionCount:3
External Links {🔗}(2)
Analytics and Tracking {📊}
- Site Verification - Google
Libraries {📚}
- Clipboard.js
- D3.js
- GSAP
- 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