-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide better error handling/notification around improper TLS setup #23
Comments
It gets tested/built on Python 2 and 3 and so should work. What version are you running? I.e. 3.X? What OS? |
Hi @atomicules ! My code:
|
It doesn't seem to be a Python3 error. I do have access to MacOS (10.14), but I have Pkgsrc on there instead of Homebrew:
works fine. This:
Looks like an issue accessing the API url. On that note, are you using the recent 2.X simplenote.py release? Simplenote closed off the old API:
|
I'm using a recent release:
How can I check wich API url? In python2 works fine.
|
Just to confirm: Python 3.6.4 (v3.6.4:d48ecebad5, Dec 18 2017, 21:07:28)
|
on
DATA_URL + params == ' https://api.simperium.com/1/chalk-bump-f49/note/index?limit=1000&data=true' |
More info: |
Weird. Wonder if it's something related to type of characters in username/password? |
Eureka! It's related with https://stackoverflow.com/questions/35569042/ssl-certificate-verify-failed-with-python3 |
Ok. Cool. Thanks for reporting back. |
Thanks. |
Doing a review of older issues. Will rename/edit this one, but basically it's up for grabs for anyone that wants to add error handling around the absence of CA certs locally, etc. |
This issue is for adding better error handling around the absence of CA certs, etc locally.
I.e. reading through the below you'll see it's not immediately obvious why simplenote.py failed.
Ideally simplenote.py should detect this as an issue and report it out as an error.
Original issue below
There's any support to python3?
sn.get_note_list(tags=[])
gets aTypeError: expected string or bytes-like object
on python3The text was updated successfully, but these errors were encountered: