Chuck, The reason to use httpretty is that it handles everything at the socket layer, this means if we change out urllib for requests or some other transport to make HTTP requests to we don't need to refactor every one of the mock/mox subouts to match the exact set of parameters to be passed. Httpretty makes managing this significantly easier (hence was the reasoning to move towards it). Though, I'm sure Jamie Lennox can provide more insight into deeper specifics as he did most of the work to convert it.
At least the above is my understanding of the reasoning. --Morgan On Wed, Nov 20, 2013 at 2:08 PM, Dolph Mathews <[email protected]> wrote: > I don't have a great answer -- do any projects depend on it other than > python-keystoneclient? I'm happy to see it removed -- I see the immediate > benefit but it's obviously not significant relative to python 3 support. > > BTW, this exact issue is being tracked here- > https://bugs.launchpad.net/python-keystoneclient/+bug/1249165 > > > > > On Wed, Nov 20, 2013 at 3:28 PM, Chuck Short <[email protected]> > wrote: >> >> Hi, >> >> I was wondering for the reason behind the usage httpretty in >> python-keystoneclient. It seems to me like a total overkill for a test. It >> also has some problems with python3 support that is currently blocking >> python3 porting as well. >> >> Regards >> chuck >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > > -- > > -Dolph > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
