Marius Gedminas

Steps to reproduce: 1. cd /tmp && mkdir example && cd example 2. virtualenv -p /usr/bin/python2.7 --no-setuptools /tmp/cleanenv 3. wget http://downloads.buildout.org/2/bootstrap.py 4. vi buildout.cfg: ``` [buildout] parts = check-manifest [check-manifest]...

Actually the interesting zest.releaser commit is https://github.com/zestsoftware/zest.releaser/commit/48ab8433.

So the thing is: `check-manifest` itself doesn't depend on setuptools. Therefore when you use it with zc.buildout, the `bin/check-manifest` script won't have setuptools added to sys.path. Therefore setting PYTHONPATH for...

@WouterVH any chance you can test this patch? I'd like to make a check-manifest release soon.

Thank you!

Hm. Should I also add a dependency on setuptools in my setup.py?

I had to revert the zc.buildout support hack because it breaks other things -- see #56.

This is complicated: we may want *.mo (created during setup.py sdist) to be in the sdist but not in the VCS, and we shouldn't warn about that.

In this particular example the .mo files aren't generated -- they're test data for the .mo parser shipped in the package.

Good point about cookies! What about ``` http get https://foo.example.com/ --connect-to 127.0.0.1:8443 ``` then? I don't like curl's `--resolve` solution (aka #362) because it requires me to repeat the host...