Add support for pip requirements + virtualenv

[xentac]

A lot of people want to be able to use greatbigcrane to manage their pip projects instead of using buildout.

Apart from parsing pip-related files, modifying and writing them again, the next hardest part will be figuring out how to run their test suites.

[dusty-phillips]

I'll do the pip part if you figure out testing. :D

[dusty-phillips]

Ok, I"m tackling this now. My plan is to make the main project page display some information useful in a pip project, with each section being editable. So it would look like a buildout recipe, but would be directly targeted. These are the sections I intend to add to the form, for starters:

• path to the location of the project's virtualenv: probably the relative path
• Requirements: Phil's amazing line editor for adding requirements to requirements.txt. For now, we'll assume this file is named requirements.txt.
• Test module: Either the name of an arbitrary python module (a custom test runner that uses discover or unittest), or a command (py.test, nose would be good examples) to run tests.

In addition, I will not display the bootstrap and buildout commands in the action lists, and I will add the following actions:

• run virtualenv --no-site-packages on the
• activate terminal: open a terminal in the source directory that has sourced the virtualenv activation script
• freeze: write a new requirements.txt from the the current status of the virtualenv
• install: install all packages in the current requirements.txt

I'll need Philized icons for all of these.

Finally, I will adjust the test commands to check if it is a pip project and run the given test command instead of the buildout command.

With those tasks done, I think we'll at least have an idea what we're working with.

[dusty-phillips]

Initial pip support is complete! I did most of what I outlined above, although I didn't bother with the freeze and activate terminal buttons for now.