Open Stack

On Mon, 28 Jul 2014, Thomas Goirand wrote:

> That's exactly the version which I've been looking at. The thing is,
> when I run the unit test with that version, it just bombs on me because
> mechanize isn't there.

How would you feel about it being optionally available and for the tests
for mechanize to only run for it if someone has aleady preinstalled
mechanize? That is the tests will skip if import mechanize is an
ImportError?

While I'm not in love with mechanize, if it is a tool that _some_
people use, then I don't want wsgi-intercept to not be useful to them.

> Please let me know if you can release a new version of wsgi-intercept
> cleaned from any trace of mechanize, or if you think this can't be done.

Let me know if the above idea can't work. Depending on your answer
I'll either release a version as described, or go ahead and flush it.
If you get back to me by tomorrow morning (UTC) I can probably get the new
version out tomorrow too.

-- 
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent