Christoph Zwerschke

The problem with this is that these are legacy packages. I'm not sure how well they are maintained and I want to keep GraphQL-core simple and not in some way...

@AlexCLeduc @jkimbo Thanks for your feedback. I understand that deferred execution (particularly for the DataLoader mechanism) without asyncio is a real world use case that we should support in some...

Something like this will eventually be integrated in GraphQL-Core, see discussion #155. Promises however will not be supported in GraphQL-Core 3 because they are not part of standard Python and...

Need to find some more time to investigate and decide. But if you have suggestions, you can comment on #155.

@jkimbo In principle, yes. Will provide some feedback soon (currently working on graphql-relay-py).

Hi @jkimbo. Thanks again for getting the ball rolling on this one. Let me recap what the problem is: Our use case is described in #71 and #148. The main...

> Django (and maybe other frameworks) currently don't support asyncio at all when interacting with the ORM and will raise an exception if you try and use it while there...

Hi @jkimbo. I have now implemented a specific DeferredExecutionContext as a subclass of the normal ExecutionContext. Instead of using DeferredValue and LazyValue classes, I have used a simple self-made synchronous...

Hi @syrusakbary, thanks for this input, great ideas. As far as I understand, these features are currently on the way of [getting into the spec](https://github.com/graphql/graphql-spec/blob/c6eb91110f6f80550f8cac1c69de1c7808b93a21/rfcs/DeferStream.md). GraphQL.js already has an experimental...

Thanks @jkimbo. I will definitely look into this again. But also like to get feedback whether this is useful or could be improved.