Marco Paolini

+1 integrating aiobotocore might be doable

+1 needed here for templating API blueprint documentation: ``` {% macro entity_one() -%} { "one": 1, "two": 2 } {% endmacro -%} + Response 200 (application/json): { "entity": [ {{...

for instance there are `str()` calls [in the wild](https://github.com/dittos/graphqllib/blob/master/graphql/core/execution/__init__.py#L305) that are craving to throw `UnicodeEncodeError:` on python 2.7

in general supporting python 2.7 _and_ python 3.3+ makes unicode handling quite tricky. I suggest using python `future` library (or `six`) to handle this consistently [here they talk about str()](http://python-future.org/compatible_idioms.html#unicode)...

@jhgg this first version kind of works https://github.com/elastic-coders/py-graphqlparser

Doh, I got all the packaging wrong in 0.0.1 ... It is fixed now (hopefully)

It's definitely doable I guess. What's your AST and visitor API? You can go ahead and open a pull request on my repo

@woodb maybe a wrapper is not even needed: `py-graphqlparser` is still experimental and I am open to changing the API at this stage. @jhgg conditional import makes sense. See `aiohttp`...

Just dumping some differences in the visitor/AST node api: **graphqlparser:** ``` python def enter_variable_definition(self, node): name = node.get_variable().get_name().get_value() ``` **graphqllib:** ``` python def enter_VariableDefinition(self, node, key, parent, path, ancestors): name...

@dittos as of now, context information is not passed in by `graphqlparser`'s visitor. I will look into it and see what can be done