search

google-code-export / gdata-python-client

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

Not able to connect #397

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Im just installed the gdata-2.0.10 under debian 4.0 X-64 , and run the sample 
code under the *gdata/samples/spreadsheet/spreadsheet.py . It producing 
following error to me. Its works for me when try this with other systems.

What is the expected output? What do you see instead?

The list of spread sheets from my account.

What version of the product are you using?

gdata-2.0.10

Please provide any additional information below.

this is the error message:-

---------------------------------

ile "spreadsheetExample.py", line 199, in <module>
    main()
  File "spreadsheetExample.py", line 194, in main
    sample = SimpleCRUD(user, pw)
  File "spreadsheetExample.py", line 42, in __init__
    self.gd_client.ProgrammaticLogin()
  File "/usr/lib/python2.5/site-packages/gdata/service.py", line 771, in ProgrammaticLogin
    headers={'Content-Type':'application/x-www-form-urlencoded'})
  File "/usr/lib/python2.5/site-packages/atom/http.py", line 163, in request
    connection.endheaders()
  File "/usr/lib/python2.5/httplib.py", line 860, in endheaders
    self._send_output()
  File "/usr/lib/python2.5/httplib.py", line 732, in _send_output
    self.send(msg)
  File "/usr/lib/python2.5/httplib.py", line 699, in send
    self.connect()
  File "/usr/lib/python2.5/httplib.py", line 1134, in connect
    sock.connect((self.host, self.port))
  File "<string>", line 1, in connect
socket.error: (110, 'Connection timed out')

---------------------------

Original issue reported on code.google.com by haridas....@gmail.com on 30 Jun 2010 at 2:18

GoogleCodeExporter commented 9 years ago 
I'm aware that this bug is very old, so marking it obsolete, but I wanted to 
mention that either a) you're behind a firewall that's not allowing connections 
to spreadsheets.google.com, or b) there was an error on our end during that 
time.  I've no evidence either way, so please re-open if you can reproduce.

Thanks,
Vic

Original comment by vicfry...@google.com on 20 Dec 2010 at 2:51