Re: [Fab-user] Paramiko 1.6.4 and paramiko.Client.connect timeout keyword arg

[Wes Winham]

Jeff,

Thanks for the advice. I've had virtualenv recommended to me multiple times by people smarter than myself, so I should probably get around to changing my process. For now I use fabric to automate building my AMIs, but I use a big list of apt packages instead of some apt and some targets for easy_install. To work around this, I just installed paramiko through easy_install and everything started working . I think I have an older version of fabric 0.1 than I use on my machine though, because it still has the issue that stops you from putting a file to a location that already doesn't exist. That's easy enough to work around for me. 

Thanks again for building such a great tool Jeff and Christian (+ others).
-Wes

On Tue, Mar 17, 2009 at 5:40 PM, Jeff Forcier <address@hidden> wrote:

Looks like a bit of an oopsie on our part. See the commit log here:

http://github.com/karmazilla/fabric/commit/27689194ca53719d21a998338ce7afc29d9fde8f

Which is post-0.1.0 :(

Myself, since I joined the project post 0.0.9 or so, I've never used
anything but Paramiko 1.7+, so perhaps it was the myriad changes
leading up to 0.1.0 that caused the dependency to change.

-Jeff

P.S. I highly suggest my personal Debian (or any other distro) Python
workflow: python, python-setuptools installed via Apt, absolutely
everything else installed (into virtualenvs if possible) via
easy_install or pip. The Python world tends to move much, much faster
than OS package maintainers are able to, unfortunately. This works
pretty well, given that I rarely need to remove a package outright,
and when I do, it's typically just removing
/usr/lib/python2.x/site-packages/$package (or just ditching my
virtualenv and recreating with whatever changed in my requirements
file).

2009/3/17 Wes Winham <address@hidden>:

> Hello,
>
> I've had great success with fabric 0.1 and earlier on my Ubuntu intrepid
> making deployments to ec2. So first off, great tool and thanks alot for your
> hard work. The issue I'm having now is with 0.1 (installed using
> easy_install) on ubuntu hardy heron. Looking at the setup.py, it says it
> requires paramiko >1.6, which I satisfy with Paramiko 1.6.4 (the
> python-paramiko package: http://packages.ubuntu.com/hardy/python-paramiko).
> The problem is that this version of paramiko doesn't seem to accept the
> timeout keyword argument to SSHClient.connect(). Version 1.7.4 of paramiko
> which I have installed on my intrepid dev machine works just fine (and that
> method accepts that argument).
>
> Is this a packaging problem or does it sound like I might have something
> more sinister going on?
>
> Thanks again,
> -Wes
>

> _______________________________________________
> Fab-user mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fab-user
>
>