Re: CloudMonkey 5.1 error

2014-05-17 Thread Daan Hoogland
On Fri, May 16, 2014 at 9:00 PM, Rohit Yadav wrote: > Hi Daan, > >> daan:~> cloudmonkey -d ~/.cloudmonkey/local.root > The first email notes, -d instead of -c I'm assuming this was a typo. yes it was, I have executed with -c afterwards and the same error resulted. > On Fri, May 16, 2014 at 11:21

Re: CloudMonkey 5.1 error

2014-05-16 Thread Rohit Yadav
Hi Daan, > daan:~> cloudmonkey -d ~/.cloudmonkey/local.root The first email notes, -d instead of -c I'm assuming this was a typo. On Fri, May 16, 2014 at 11:21 PM, Daan Hoogland wrote: > I didn't think of the old frameworks but these don't contain any but > vboxapi. Do you think this has anythin

Re: CloudMonkey 5.1 error

2014-05-16 Thread Daan Hoogland
I didn't think of the old frameworks but these don't contain any but vboxapi. Do you think this has anything to do with it? I uninstalled and installed cloudmonkey several times and I checked that it was really gone in between. On Thu, May 15, 2014 at 5:19 PM, Rohit Yadav wrote: > Try this: > >

Re: CloudMonkey 5.1 error

2014-05-16 Thread Rohit Yadav
Try this: `which cloudmonkey` and try to debug which path the runnable script is trying to execute? I'm not sure what's causing issue, probably some path issue. You may remove cloudmonkey using pip uninstall cloudmonkey and rm -fr from 2.7 and possibly 2.6 in /Library/Python/{2.6,2.7 etc.} and do

Re: CloudMonkey 5.1 error

2014-05-14 Thread Daan Hoogland
request is available. I can run cloudmonkey without the wrapper script: python /Library/Python/2.7/site-packages/cloudmonkey/cloudmonkey.py -c ~/.cloudmonkey/local.root works but cloudmonkey -c ~/.cloudmonkey/local.root gives the error On Wed, May 14, 2014 at 9:33 AM, Rohit Yadav wrote: > Hi

Re: CloudMonkey 5.1 error

2014-05-14 Thread Rohit Yadav
Hi Daan, Can you do pip install requests and retry? Looks like requests (used to sane http calls) library is not available on your system. I'll try to re-read the code this weekend. Regards. On Fri, May 9, 2014 at 10:39 PM, Daan Hoogland wrote: > Not sure if this is a bug in code or in user: >