smiley

I think true native support (i.e.: mapping "is this certificate okay?" requests to OS APIs) would be preferable. This would help with the problem of automatically-updating certificate stores on Windows,...

@mwcampbell External dependencies could result in cases of version conflicts. One application could require `pyOpenSSL` in a specific version, while `requests` needs another. In some cases, (mostly enterprise) you're locked...

I looked into how Chrome integrates with Windows' SSL/TLS certification validation and all it takes is a few simple API calls. I have a proof-of-concept in C that can be...

Finally got around to doing the Windows implementation, and it looks like the configurable callback in PyOpenSSL's [`Context.set_verify(mode, callback)`](https://pyopenssl.readthedocs.org/en/latest/api/ssl.html#OpenSSL.SSL.Context.set_verify) will be a good place to implement this. (as @Lukasa suggested)...

Huh, weird. The server originally didn't mind and some examples used the `v000x` syntax, while others used `vx`. (Any amount of zeroes worked) Maybe the server-side implementation changed and broke...

I still see it... No need to bump it, that just sends another email my way. Right now there's no ETA because I'm busy with a lot of other things....

Sadly no, due to the same reason as before. I'm busy with too many other things. This will still be done, it's just on hold for now.

Oh, forgot about this decorator issue. Does this screw up any other functions/classes? I'll fix this, but APIConnection will soon be retired for an instance-based solution (like APIInterface in the...

This is proving to be quite an issue. While Requests natively supports asynchronous requests, it requires gevent, which just isn't easy to install and use on Windows, at least on...

That's actually what I'm currently using for caching object properties. What I proposed on this issue is to move caching _from properties_ to _requests_, so I could cache the raw...