Agreed. That was the previous behavior. Now you have to add =s0 to the result of the get_serving_url, passing 0 as string does not work.
The API should not have changed behavior and the new behavior is not logical. Why should I have to specify the size as 0 if what I want is the original image? Why should the default use case, to return a resized image? This is clearly a cost cutting measure by Google as a 512x512 image should be smaller and cost less to serve. Google is betting most devs wont change their code. On Dec 9, 9:11 pm, Andreas <[email protected]> wrote: > this should not make any difference. > > >>> size = 0 > >>> '%s' %size > > '0' > > the problem is that the behaviour is not right to me. if i dont specify a > size the original (up to a max of 1600px) should be returned and not a > resized version. > another non logic thing is that passing 0 returns a not resized image. > > not really straight forward. > > On Dec 9, 2011, at 4:05 PM, Kyle Finley wrote: > > > > > Could you pass 0 as a string? > > > url = get_serving_url(key, size="0") > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To view this discussion on the web > > visithttps://groups.google.com/d/msg/google-appengine/-/CQ1IcMtqWvkJ. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
