<html><body><p><tt>Cory Benfield <cory@...> writes:</tt><br><tt>> > The problem that occurs is the result of a few interacting things:<br>> > - requests has very very specific versions of urllib3 it works with.<br>> > So specific they aren't always released yet.<br>> <br>> This should no longer be true. Our downstream redistributors pointedout to us<br>> that this was making their lives harder than they needed to be, so it's now<br>> our policy to only update to actual release versions of urllib3.</tt><br><br><tt>That's great... except that I'm confused as to why requests would continue to repackage urllib3 if that's the case. Why not just prereq the version of urllib3 that it needs? I thought the one and only answer to that question had been so that requests could package non-standard versions.</tt><br><BR>
</body></html>