urllib2 doesn't exist within python3. The proposed changes should be compatible with python2 and 3, tested on 2.7.13 and 3.6.0.

Sorry looks like I commited this early without running more tests, let me refine & push a new update to fix compatibility with both Python2 and 3.

`from setuptools import setup

with open('README.md', 'r') as fh: long_description = fh.read()

graphqlclient-0.2.2/ graphqlclient-0.2.2/PKG-INFO graphqlclient-0.2.2/graphqlclient/ graphqlclient-0.2.2/graphqlclient/client.py graphqlclient-0.2.2/graphqlclient/init.py graphqlclient-0.2.2/setup.py graphqlclient-0.2.2/setup.cfg graphqlclient-0.2.2/graphqlclient.egg-info/ graphqlclient-0.2.2/graphqlclient.egg-info/PKG-INFO graphqlclient-0.2.2/graphqlclient.egg-info/not-zip-safe graphqlclient-0.2.2/graphqlclient.egg-info/SOURCES.txt graphqlclient-0.2.2/graphqlclient.egg-info/requires.txt graphqlclient-0.2.2/graphqlclient.egg-info/top_level.txt graphqlclient-0.2.2/graphqlclient.egg-info/dependency_links.txt`

Hi, thanks for this nice little library!

I ran into a weird issue when using python 3.7 where I would get a certificate error as follows:

urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1045)>

The reason why this is weird is because I ran the exact same snippet with python 2.7 and everything worked nicely! Any idea on what might cause this ? Thanks!

AWS AppSync uses x-api-key instead of Authorization, so I have a need to vary this. I've left it in such a way that 'Authorization' is the default if not specified, to keep this change backwards compatible.

Since the string starts with {}, this will be interpreted as a key in python's String.format function. What is the best way to programatically include values into the query?

User should be able to compose their own authorization header. For example AWS API Gateway using Cognito User Pool can not check Authorization header token which has Bearer

Allow for _send to fail silently without printing the error message. Often it is useful to handle (and print) the error outside the _send function. This commit adds a print_err argument (defaults to True), so to suppress the error printing one can simply set this to False.

This should be especially useful if more sophisticated error handling and logging is implemented to customize the errors without having prints that are neither formatted nor have any debug level associated to it.

i am using this client, but sometimes i get below error, when i checked client.py, i dont see socket connection is closed internally. pls check

ResourceWarning: unclosed <ssl.SSLSocket fd=7, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('10.166.23.90', 62047), raddr=('52.217.16.132', 443)> outcome.errors.clear() ResourceWarning: Enable tracemalloc to get the object allocation traceback

Changes made:

• Using requests instead of urllib
• Letting exceptions propagate to caller instead of catching and rethrowing
• Added generic header injection
• Deserialize JSON into dict for easier processing

when using this client externally, the user sometimes does not want the response to be printed out.

this PR replaces the print statements with logging.debug statements. if you think this change makes sense but want more flexibility around the log level, i'm willing to extend this PR as well.

thanks a lot!

I also found that I was always parsing the response for json so I just made that a built in option. I realize that this is a breaking change for most people, so I am submitting it as a seperate PR.

Hope that you do not find this annoying, I am only trying to make the software world a better place.