Commented above as a reply to @calpaterson; I'll paste the same comment below.

> I wrote about this in the FAQ (https://github.com/qw3rtman/p#faqs), but I'll reiterate the main use case below.

> p is for the average Python developer who just needs to work with a different version of Python. Suppose one wants to start using the latest development release of Python; they just run `p latest` and p will take care of the rest.

> `p` is a wrapper that handles and manages everything for you, simplifying the process for those who aren't familiar with tox or virtualenvwrapper. :)

I wrote about this in the FAQ (https://github.com/qw3rtman/p#faqs), but I'll reiterate the main use case below.

p is for the average Python developer who just needs to work with a different version of Python. Suppose one wants to start using the latest development release of Python; they just run `p latest` and p will take care of the rest.

`p` is a wrapper that handles and manages everything for you, simplifying the process for those who aren't familiar with tox or virtualenvwrapper. :)

At this point, p makes no attempt to manage pip versions. I have added this feature to the TODO and it will be implemented sometime in the future.

Thanks for the suggestion! :)

I was so caught up in training Ralph, I forgot to add a license!

I've settled on GNU GPL v3. Thanks for the catch. :)

And I just settled on never using this. Why would you pick GPL v3... Shell scripts are the last place I want to argue with the company lawyer about.

I'd like to politely suggest you consider changing the license before you accept contributions. The smaller the tool and the more modularity it has within a software stack (shell script helpers are extremely modular) the more appropriate it is to license it something towards the MIT license end of the strong - weak copyleft spectrum.

I'm a 15-year-old who wrote a fairly successful (800+ stars on GitHub!) wrapper for Git.

That's fantastic!

What if someone adds in a .gitignore file that ignores everything except for itself?

Evil? >:D

He asked not being a dick, no?

I am currently working on support for branches, which I hope to release in the near future.

Thanks for the feedback! :)

The only output I didn't fully design on my own was the log command (`gg l`). I used information found on this Gist (https://gist.github.com/textarcana/1306223) to retrieve the log information in JSON. From there, I designed an output style on my own.

Hope that answers your question. :)

I replied to bcl here about that here: https://news.ycombinator.com/item?id=9166363.

Branches are a planned feature, check the TODO.

If you would like to contribute to the addition of branches, that would be great. :)