Use of 'async' variable name breaks erequests on 3.7 and later about erequests HOT 3 CLOSED

It's slightly more annoying than that, alas: the API currently exposes the methods in that async namespace. erequests.async.get() for example. I think it would be a good idea to get rid of the async there altogether and say that the methods exposed by this library are async, period.

If you feel like sending a patch, PRs are welcome :-)

from erequests.

Oh derp, I hadn't actually looked at the async functions. Don't submit issues at 1 AM, kids.

I'm not sure exactly what you'd want from a PR. I don't see any way to avoid breaking the API for the async functions, but leaving the non-async ones intact would hopefully minimize the damage. Would removing the async references and just replacing them with a bunch of get_async etc. methods work for you?

from erequests.

Yeah, that would work!

from erequests.