You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After imputting:
import pygr
from pygr import worldbase
dir(worldbase)
I see:
Traceback (most recent call last):
File "C:\Python27\lib\site-packages\pygr-0.8.2-py2.7-win32.egg\pygr\metabase.py", line 1085, in update
self, **mdbArgs)
File "C:\Python27\lib\site-packages\pygr-0.8.2-py2.7-win32.egg\pygr\metabase.py", line 915, in __init__
storage = XMLRPCMetabase(dbpath, self, **kwargs)
File "C:\Python27\lib\site-packages\pygr-0.8.2-py2.7-win32.egg\pygr\metabase.py", line 335, in __init__
self.server = get_connection(url, 'index')
File "C:\Python27\lib\site-packages\pygr-0.8.2-py2.7-win32.egg\pygr\coordinator.py", line 94, in __call__
return s[name] # GET THE REQUESTED OBJECT PROXY FROM THE SERVER
File "C:\Python27\lib\site-packages\pygr-0.8.2-py2.7-win32.egg\pygr\coordinator.py", line 75, in __getitem__
methodDict = self.server.objectInfo(name)
File "C:\Python27\lib\xmlrpclib.py", line 1224, in __call__
return self.__send(self.__name, args)
File "C:\Python27\lib\xmlrpclib.py", line 1575, in __request
verbose=self.__verbose
File "C:\Python27\lib\xmlrpclib.py", line 1264, in request
return self.single_request(host, handler, request_body, verbose)
File "C:\Python27\lib\xmlrpclib.py", line 1294, in single_request
response = h.getresponse(buffering=True)
File "C:\Python27\lib\httplib.py", line 1027, in getresponse
response.begin()
error: [Errno 10060] A connection attempt failed because the connected party did
not properly respond after a period of time, or established connection failed because connected host has failed to respond
WARNING: error accessing metabase http://biodb2.bioinformatics.ucla.edu:5000.
Continuing...
[]
>>>
Original issue reported on code.google.com by els...@gmail.com on 24 Mar 2012 at 4:22
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
els...@gmail.com
on 24 Mar 2012 at 4:22The text was updated successfully, but these errors were encountered: