-
Notifications
You must be signed in to change notification settings - Fork 99
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
Old-style classes interfere with returning strings #22
Comments
Did more digging into this error. Seems that tomorrow breaks if any type-checking whatsoever is done on the resulting object. So passing the results into most any library function should break. |
Super valid complaint. It's actually unrelated to the kind of class being used -- it's simply that calls to You can fix this by doing literally anything to the result object before calling a function that checks the results type. I would recommend calling import base64
import json
from tomorrow import threads
import requests
def save_image_json(images, filename):
with open(filename, 'a') as sink:
for i, image in enumerate(images):
results = return_image_json(image)
results._wait()
sink.write(results)
@threads(4)
def return_image_json(image_link):
response = requests.get(image_link)
encoded = "data:%s;base64,%s" % (response.headers['Content-Type'], base64.b64encode(response.content))
return json.dumps({image_link: encoded}) + '\n'
if __name__ == "__main__":
# koala images
images = [
'http://i.imgur.com/1p5nKyZ.jpg',
'http://i.imgur.com/lDt3nJ8.jpg',
'http://i.imgur.com/hkUeCBT.jpg',
'http://i.imgur.com/ZglSElj.jpg'
]
save_image_json(images, filename='koalas.json') I'm going to look into forcing |
if I have the error after run code,what I get is all the Tomorrow class. Is there any method to deal with it? |
I have no idea how to solve this one, but when trying to return strings from a function decorated with an @threads, rather than executing, it simply errors. Code below to reproduce:
It looks like moving to new-style classes resolves this issue, but since you're relying on some of the syntax-hacks of old-style classes I'm not sure if this is solvable.
The text was updated successfully, but these errors were encountered: