Please make disable_warnings=0 turn warnings back on?

[mentalisttraceur]

It looks like the code only ever globally turns warnings off, but can never turn them back on again.

I have a situation where I need to follow best-practices and only narrowly silence warnings for a single GET request, which generates spurious and expected warnings, but then expose warnings as normal for all other calls.

So it would be really great if disable_warnings=0 turned all of the warnings back on.

(Currently I'm working around this by just exposing our own custom keywords that adjust the urllib3 warnings and log level at the most narrow granularity possible, but I think it would be better to have this functionality in the library.)

[mentalisttraceur]

I just realized I initially worded the subject line of this issue in a way that could be read as a command or demand.

That was not my intent - I was just trying to be concise - so I have now adjusted it accordingly to reduce the potential for that interpretation.