GITHUB . COM {}

Matching Content Categories {📚}

• Video & Online Content
• Careers
• Technology & Computing

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,666,394 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,347,507 paying customers.
The estimated monthly recurring revenue (MRR) is $22,459,531.
The estimated annual recurring revenues (ARR) are $269,514,368.

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

venv, pipenv, empty, directory, issue, file, entire, deleted, sign, projects, environment, pull, requests, virtualenvs, project, kobayashi, navigation, pypa, actions, security, closed, description, localsharevirtualenvs, find, running, command, install, added, commit, references, github, labels, milestone, footer, skip, content, menu, product, solutions, resources, open, source, enterprise, pricing, search, jump, public, notifications, fork, star,

Topics {✒️}

kobayashi/4790-handle-empty-dot-venv local/share/virtualenvs directory run pipenv --rm venv pipenv --rm local/share/virtualenvs 0c8fb2f stewartmiles added personal information empty kobayashi mentioned comment metadata assignees issue description entire virtualenvs directory handle empty projects earlier labels projects projects milestone empty directory pipenv version 2021 pipenv --python 3 remain empty empty file entire directory venv fails project environment venv file pipenv pipfile present error message project folder /users/myname/ big loss workon home project root assigned labels milestone relationships actual command github empty verified 2636992 sign virtualenvs share venv environment deleted entire ~/ file command sign skip jump macos

Payment Methods {📊}

• Braintree

Questions {❓}

• Already have an account?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:Empty .venv file causes entire virtualenvs directory to be deleted
      articleBody:### Summary if `.venv` is an empty file and I run `pipenv --rm`, the entire `~/.local/share/virtualenvs` directory is deleted. This happens even when there's no `Pipfile` present. This is on macOS, pipenv version 2021.5.29. ### Issue description I was messing around with my project environment, and tried to tell my editor where to find the environment by putting it in `.venv`. Turns out that running `pipenv --venv > .venv` fails because it first touches `.venv`, and then the actual command looks at the empty `.venv` and doesn't find an environment. This causes the file to remain empty. (The command did print an error message in STDERR, but somehow I didn't notice it immediately.) So now with an empty `.venv` in my project folder, I ran `pipenv install <some package>` and wondered why it said it had to create a new virtualenv. I looked at the output more closely and realized that the new env was created in `/Users/myname/.local/share/virtualenvs` (not in a subdirectory). I got curious about what would happen if I now tried to scrap the thing, and as I feared, running `pipenv --rm` deleted that entire directory, which contained all the other virtualenvs that I had made with Pipenv for other projects earlier. It wasn't a big loss or I wouldn't have tried, but still not something I like to see happening. ### Steps to replicate In an empty directory: ``` touch .venv pipenv --rm ``` Now the entire `~/.local/share/virtualenvs` directory is deleted. The way I ended up in this situation was actually essentially the following: ``` pipenv --python 3.9 pipenv --venv > .venv pipenv install requests pipenv --rm ```
      author:
         url:https://github.com/dronir
         type:Person
         name:dronir
      datePublished:2021-09-16T20:47:55.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:1
      url:https://github.com/4790/pipenv/issues/4790
      context:https://schema.org
      headline:Empty .venv file causes entire virtualenvs directory to be deleted
      articleBody:### Summary if `.venv` is an empty file and I run `pipenv --rm`, the entire `~/.local/share/virtualenvs` directory is deleted. This happens even when there's no `Pipfile` present. This is on macOS, pipenv version 2021.5.29. ### Issue description I was messing around with my project environment, and tried to tell my editor where to find the environment by putting it in `.venv`. Turns out that running `pipenv --venv > .venv` fails because it first touches `.venv`, and then the actual command looks at the empty `.venv` and doesn't find an environment. This causes the file to remain empty. (The command did print an error message in STDERR, but somehow I didn't notice it immediately.) So now with an empty `.venv` in my project folder, I ran `pipenv install <some package>` and wondered why it said it had to create a new virtualenv. I looked at the output more closely and realized that the new env was created in `/Users/myname/.local/share/virtualenvs` (not in a subdirectory). I got curious about what would happen if I now tried to scrap the thing, and as I feared, running `pipenv --rm` deleted that entire directory, which contained all the other virtualenvs that I had made with Pipenv for other projects earlier. It wasn't a big loss or I wouldn't have tried, but still not something I like to see happening. ### Steps to replicate In an empty directory: ``` touch .venv pipenv --rm ``` Now the entire `~/.local/share/virtualenvs` directory is deleted. The way I ended up in this situation was actually essentially the following: ``` pipenv --python 3.9 pipenv --venv > .venv pipenv install requests pipenv --rm ```
      author:
         url:https://github.com/dronir
         type:Person
         name:dronir
      datePublished:2021-09-16T20:47:55.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:1
      url:https://github.com/4790/pipenv/issues/4790
Person:
      url:https://github.com/dronir
      name:dronir
      url:https://github.com/dronir
      name:dronir
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:1
      interactionType:https://schema.org/CommentAction
      userInteractionCount:1

External Links {🔗}(2)

• How much does https://github.blog bring in each month?
• Explore the financials of https://www.githubstatus.com/

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