GITHUB . COM {}

Matching Content Categories {📚}

• Dating & Relationships
• Education
• Mobile Technology & AI

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,653,586 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 {💳}

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,011 paying customers.
The estimated monthly recurring revenue (MRR) is $22,327,244.
The estimated annual recurring revenues (ARR) are $267,926,929.

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

ronnypfannschmidt, pyargs, packages, commented, namespace, package, scottpurdy, import, pytest, zope, zopeqwer, found, importing, member, sign, issue, file, type, projects, understand, github, eggs, zopeasdf, work, python, support, bug, status, mentioned, enkore, navigation, open, code, pull, requests, actions, security, pytestbot, bitbucket, wosc, resolution, installed, layout, zopeasdfegg, fine, directory, doesnt, mechanism, resolve, entry,

Topics {✒️}

org/pytest-dev/pytest/issue/478 activity assigned labels status understand namespace packages pip install --egg supports namespace packages personal information --pyargs support collecting tests relevant code super high priority modern packaging tools comment metadata assignees random matching entry test miraculously gloss site-packages/zope support zip importing support zipfile importing test --pyargs zope eggs im thinking ronnypfannschmidt mentioned type projects top level package python import mechanism means import zope projects milestone py lets py asdf/zope/__init__ issue topic type addressed type namespace package contributing packages pyargs resolution entry points discovery mechanism time import zope egg py test collector import system setuptools mess import pkg_resources forgotten __init__ missing __init__ supporting module resolve zope finding zope unzip zope wolfgang schnerring iteratively importing iteratively pop

Payment Methods {📊}

• Braintree

Questions {❓}

• Already have an account?
• Are eggs really being phased out?
• Does it work for packages though?
• If a fix is complex, maybe just print a hint?
• Instead of iteratively importing from the top level package, could it try importing from the full path first and, if it fails, iteratively pop the rightmost element off until it succeeds in importing and then do the file lookup from there?
• Path just like entry points of setuptools?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:--pyargs does not understand namespace packages
      articleBody:Originally reported by: **Wolfgang Schnerring (BitBucket: [wosc](http://bitbucket.org/wosc), GitHub: [wosc](http://github.com/wosc))** --- The pyargs resolution does not understand namespace packages when the different contributing packages are installed as eggs (which is the layout used by zc.buildout and also `pip install --egg`, see http://peak.telecommunity.com/DevCenter/setuptools#namespace-packages). It looks like this: ``` site-packages/ zope.asdf.egg/ zope/ asdf/ ... zope.qwer.egg/ zope/ qwer/ ... ``` This is a well supported layout, which means `import zope.asdf` and `import zope.qwer` work just fine (the specification is something to the effect of, if there is more than one directory that claims to be package "zope", there is no guarantee which one you will actually get when you say `import zope`, but all subpackages will be accessible regardless). But `py.test --pyargs zope.asdf` will work, while `py.test --pyargs zope.qwer` will say "file or package not found" (it might also be the other way around, so zope.qwer works, but zope.asdf doesn't). This is because `_pytest.main.Session._tryconvertpyarg` does not actually rely on the Python import mechanism to do the resolution (I'm not sure why, I'm guessing it's to support collecting tests outside of packages?). Instead it splits the argument on dots and loads the **parts** from the import system, assuming their filesystem location is the one that matters -- which is incorrect. In the example, trying to resolve `zope.qwer`, it will first resolve `zope`, which results in a random matching entry, e.g `site-packages/zope.asdf/zope/__init__.py`. It then assumes that the rest of the name must exist below _this specific_ directory, thus never finding `zope.qwer`. --- - Bitbucket: https://bitbucket.org/pytest-dev/pytest/issue/478
      author:
         url:https://github.com/pytestbot
         type:Person
         name:pytestbot
      datePublished:2014-03-06T14:18:30.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:13
      url:https://github.com/478/pytest/issues/478
      context:https://schema.org
      headline:--pyargs does not understand namespace packages
      articleBody:Originally reported by: **Wolfgang Schnerring (BitBucket: [wosc](http://bitbucket.org/wosc), GitHub: [wosc](http://github.com/wosc))** --- The pyargs resolution does not understand namespace packages when the different contributing packages are installed as eggs (which is the layout used by zc.buildout and also `pip install --egg`, see http://peak.telecommunity.com/DevCenter/setuptools#namespace-packages). It looks like this: ``` site-packages/ zope.asdf.egg/ zope/ asdf/ ... zope.qwer.egg/ zope/ qwer/ ... ``` This is a well supported layout, which means `import zope.asdf` and `import zope.qwer` work just fine (the specification is something to the effect of, if there is more than one directory that claims to be package "zope", there is no guarantee which one you will actually get when you say `import zope`, but all subpackages will be accessible regardless). But `py.test --pyargs zope.asdf` will work, while `py.test --pyargs zope.qwer` will say "file or package not found" (it might also be the other way around, so zope.qwer works, but zope.asdf doesn't). This is because `_pytest.main.Session._tryconvertpyarg` does not actually rely on the Python import mechanism to do the resolution (I'm not sure why, I'm guessing it's to support collecting tests outside of packages?). Instead it splits the argument on dots and loads the **parts** from the import system, assuming their filesystem location is the one that matters -- which is incorrect. In the example, trying to resolve `zope.qwer`, it will first resolve `zope`, which results in a random matching entry, e.g `site-packages/zope.asdf/zope/__init__.py`. It then assumes that the rest of the name must exist below _this specific_ directory, thus never finding `zope.qwer`. --- - Bitbucket: https://bitbucket.org/pytest-dev/pytest/issue/478
      author:
         url:https://github.com/pytestbot
         type:Person
         name:pytestbot
      datePublished:2014-03-06T14:18:30.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:13
      url:https://github.com/478/pytest/issues/478
Person:
      url:https://github.com/pytestbot
      name:pytestbot
      url:https://github.com/pytestbot
      name:pytestbot
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:13
      interactionType:https://schema.org/CommentAction
      userInteractionCount:13

External Links {🔗}(5)

• Income figures for https://github.blog
• What's the income of http://bitbucket.org/wosc?
• How much does http://peak.telecommunity.com/DevCenter/setuptools#namespace-packages make?
• How profitable is https://bitbucket.org/pytest-dev/pytest/issue/478?
• Monthly income for https://www.githubstatus.com/

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