Open Stack

On Sun, 27 Jul 2014, Thomas Goirand wrote:

> I don't think you get it. The question isn't to "fix Trove to be
> ready for Py3.4", we're very far from that. The question is: how can I
> maintain the python-wsgi-intercept package in Debian, when it now
> depends on a very bad package in the newer version that I need to
> upgrade to. And how can I continue to have it work in Debian Jessie for
> the soon-to-come freeze deadline of the 5th of November. So I'm more
> concerned by Icehouse right now, and not even remotely thinking about
> the K release.

I maintain wsgi-intercept, and I'm happy to remove mechanize if that's
really necessary. I didn't want it in there but when someone asked for
it to be back in there was insufficient objection so back in it went.

     https://github.com/cdent/python3-wsgi-intercept/pull/16

If it is causing problem, then by all means say so.

In any case, mechanize shouldn't be _required_, it should just be
available if you ask for it. If you don't import
wsgi_intercept.mechanize_intercept mechanize will not be loaded, and if
you try to do so with Python 3 you'll get an AssertionError and the
world will crash around you.

Maybe you aren't looking at the most recent version (0.7.0)?

If there are issues please report them as bugs on github, they'll
get fixed:

     https://github.com/cdent/python3-wsgi-intercept/issues

If there's a better way to do the optional-ness of mechanize
(without changing everything else), then please suggest something.

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