Elias Gabriel

@laurentS cool! if you cannot manage to get your PR merged, and its been a year so that might not be likely, another option would just be to just include...

@laurentS hey, i threw together a draft PR for migrating the library over to async/await. Obviously `limits` is still blocking, but its wrapped in a threaded executor so it doesn't...

@samuel-lucas6 @schollz I've started a PR for adding the twisted Edwards25519 curve into PAKE. It's not the exact same curve, but birationally equivalent so effectively would close this issue if...

i like the `version-compat` concept (though open to other, possibly clearer, names). I can draft a PR and see how things turn out.

I am encountering the same bug when trying to make my library work across python versions. With the following, I would expect the dep to be `0.19` on `3.7` and...

@Jamim apologies if you're on the Discord, your username didn't pop up when searched -- have you made progress on this, by chance?

i also am getting this error, running on Ubuntu 22.04 and Node v20.10.0 with Yarn 4.1.1: ``` Error: Expected DataContext to already have been set via setCtx. If this is...

if anyone comes across this in the future and is using Yarn PnP, you can resolve this error by telling yarn to unplug the package at install time package.json ```json...

I'm able to reproduce this behavior. If I pull the `Set-Cookie` header out the response and pass it into `http.cookies.SimpleCookie`, I can fetch the value perfectly fine. The code I...

> Likely this issue is the same as #6245 Perhaps it extends beyond missing domains and has something to do with not FQ domains? Because in my case, it doesn't...