Christoph Zwerschke

@asgoel, thanks for reporting the issue. As far as I see, you really need to build your own graphql() function to do that. But I have forwarded your question to...

We should consider all options, but the API should be backward compatible, to not cause another turmoil in the GraphQL-Python ecoystem, and the code and API should not deviate too...

> I think this already happens with the sync execution pathway but I don't think it's possible to always return True for async schema's because the default resolver is still...

See also #101 for performance optimization.

For the records: In #142 the locally defined async methods were moved to the class level, but this did not make things better. The next step could be to create...

It's currently not supported. You can serialize a schema to SDL using `print_schema`. But you can't pickle a schema because of the resolvers functions and also because GraphQL-core uses lambdas...

@rpgreen Interesting. Maybe it would be worthwile then to profile why/where `build_schema()` is so slow and whether there is potential for optimization. First step would be to find out whether...

Thanks @erikwrede for the profiling. Did you use the latest version (3.2.1) of GraphQL-core? I'm asking because there have been some speedups and get_visit_fn is actually deprecated.

@rpgreen I have looked into this a bit more. It seems you want to pickle only schemas that have been produced from SDL, which makes this issue a bit more...

Btw, I have added a test for pickling schemas [here](https://github.com/graphql-python/graphql-core/blob/5101d3920bbda58382a35b97600120d526945261/tests/utilities/test_build_ast_schema.py#L1189) which is currently skipped.