search

prayagverma / gdata-python-client

Automatically exported from code.google.com/p/gdata-python-client
1 stars 0 forks source link

NoneType: gdata.docs.data.Resource.acl_feed #589

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.  feed_uri_with_acl = 'https://docs.google.com/feeds/default/private/expandAcl
2. feed = client.GetResources(feed_uri_with_acl)

3. feed.entry[0].acl_feed

What is the expected output? What do you see instead?
Expected: AclFeed
Instead: 
         type(feed.entry[0].acl_feed)
         <type 'NoneType'>

What version of the product are you using?
gdata-2.0.16

Please provide any additional information below.

I don't know if this has ever worked. This is the first time I'm trying to use 
it.

Thanks Vic.

Ashwini

Original issue reported on code.google.com by r...@majestik.net on 29 Jan 2012 at 9:23

GoogleCodeExporter commented 9 years ago 
Yes, this likely won't work as it expandAcl projection is a new feature in the 
API.

Original comment by afs...@google.com on 2 Feb 2012 at 2:43

GoogleCodeExporter commented 9 years ago

Original comment by afs...@google.com on 2 Feb 2012 at 2:44

GoogleCodeExporter commented 9 years ago

Original comment by afs...@google.com on 2 Feb 2012 at 2:51

GoogleCodeExporter commented 9 years ago 
Sorry, I was wrong about this, the acl_feed element should be populated 
correctly for your URI. Could you paste a copy of the XML you are getting in 
your entry?

Original comment by afs...@google.com on 13 Feb 2012 at 3:43

GoogleCodeExporter commented 9 years ago 
Yes sir, zip file attached. 

I included XML output for feed.entry[0] with and without expandAcl, as well as 
the URI's I used. It looks like the data is there, but acl_feed can't see it. 

type(feed.entry[0].acl_feed)
<type 'NoneType'>

Thanks Ali!

Ashwini

Original comment by r...@majestik.net on 15 Feb 2012 at 6:15

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks for this. I checked and it seems that there is a bug somewhere. I will 
investigate if it is in the client library or in the API. I suspect the client 
library.

Original comment by afs...@google.com on 15 Feb 2012 at 6:54