Re: [Fab-user] Current head passing unit tests?

[Jeff Forcier]

Oh, one other thing, if you're still getting deprecation warnings on
2.6, you probably do *not* have the latest code -- I put in a patch
for that around the same time as I fixed the lint brokenness. This
implies you might not actually have the latest code -- though if
things import fine on the command-line that sort of dashes this theory
(and strengthens the "your nose environment differs from your normal
one" theory.)

I just checked and Github is still getting all my commits, so it is up to date.

-Jeff

On Sat, Aug 22, 2009 at 2:34 PM, Jeff Forcier<address@hidden> wrote:
> Hey Steve,
>
> On my system (virtualenv with Python 2.5.1 on OS X 10.5) and with
> things fully updated, I can run the test suite on both master and 0.9
> branches without issue, so it is likely to be something on your end.
>
> Has anything else changed since you last ran the test suite? it
> definitely seems like some wide-ranging import problem; perhaps your
> copy of Nose is broken somehow?
>
> I have a Python 2.6 VM at work, but not here at home; I'll set one up,
> since I should have one handy, and will try to confirm that a fresh
> dev setup works on 2.6 as well.
>
> Finally, I *did* break some imports a few days to a week ago when
> doing a bunch of Lint-based cleanup, but as far as I can tell I caught
> and fixed all of it soon afterwards -- I again point to the test suite
> working on my system as hopeful proof of this.
>
> -Jeff
>
> On Sat, Aug 22, 2009 at 2:17 PM, Steve Steiner
> (listsin)<address@hidden> wrote:
>> Sorry if this ends up being a dupe; sent from the wrong e-mail first time...
>>
>> S
>>
>> Hey, quick question for anyone who could try it real quick...
>>
>> Fab is installed in develop mode, just updated from github a few minutes
>> ago.
>>
>> I'm trying to run Fabric's unit tests off the head with `fab test`  and I
>> get:
>>
>> (wssw1)ssteiner:(git)fabric[master]/$ fab test
>> [localhost] run: nosetests -sv --with-doctest
>> Failure: ImportError (cannot import name output) ... ERROR
>> ... 8 more times
>>
>> Failure: ImportError (cannot import name HostConnectionCache) ... ERROR
>> .. twice
>>
>> Failure: ImportError (No module named fudge.patcher) ... ERROR
>> ...a couple of times
>>
>> Failure: ImportError (No module named paramiko) ... ERROR
>>
>> test_version.test_get_version('0.9', '0.9') ... ok
>> ... and the rest of the version tests pass
>>
>> All of the imports that are failing are working fine from a command-line
>> Python interpreter and it's the same interpreter `fab` is using.
>>
>> Part of it seems to be a cascade from trouble finding paramiko because the
>> traceback shows, in part:
>>
>>  File "/Users/ssteiner/Dropbox/work/fabric/fabric/state.py", line 9, in
>> <module>
>>    from fabric.network import HostConnectionCache
>>  File "/Users/ssteiner/Dropbox/work/fabric/fabric/network.py", line 19, in
>> <module>
>>    abort("paramiko is a required module. Please install it:\n\t$ sudo
>> easy_install paramiko")
>>  File "/Users/ssteiner/Dropbox/work/fabric/fabric/utils.py", line 16, in
>> abort
>>    from fabric.state import output
>> ImportError: cannot import name output
>>
>> Anyone have a clue what's going on here?
>>
>> This is Python 2.61 in a virtualenv on OS X.  I can import paramiko and
>> fabric.state.output just fine (with deprecation warnings) from a prompt and
>> I've checked to see that the same Python binary's being used by the fab
>> command line tool.
>>
>> Thanks,
>>
>> S
>>
>>
>>
>> _______________________________________________
>> Fab-user mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/fab-user
>>
>