Add to homebrew? about mitmproxy

[cortesi]

I might be wrong, but I believe that homebrew has a policy against including packages that can be installed by pip or other external package managers. The next release of mitmproxy will be installable by pip...

[zenspider]

Current version doesn't say how to install it. Ya need to have one or the other. I'd love to use this but it flips my bozobit.

[cortesi]

Not sure what you mean by flipping your bozo bit, but the easiest way to install mitmproxy at the moment is using pip, the most widely used Python package manager. The command is simple, and is right there on the front page of mitmproxy.org:

pip install mitmproxy

[zenspider]

You should add that to the readme.

[zenspider]

BTW, I don't think homebrew has a policy against packages that can be installed via a package manager, but those that have to be installed by a package manager.

[cortesi]

If you're reading the README you've either downloaded a source distribution or checked out the source. At that point, it's unavoidable that you need to know what a Python package is and how to install it. I'll consider spelling this out in the README, but there's a point beyond which it no longer makes sense to hand-hold.

[cortesi]

Regarding homebrew, I've now looked at the situation, and it's probably not appropriate for mitmproxy. Not only would a mitmproxy recipe need to be created, but the same would need to be done for the libraries it depends on. This won't fly - the convention is to install this sort of thing through pip or easy_install.

[zenspider]

1. Your readme is prominently displayed at: https://github.com/cortesi/mitmproxy/

2. Your instructions don't help non-python developers who just want to use your software:

9551 % type pip
whatis: pip: not found
9552 % python --version
Python 2.7.1