It's Github's fault! :( so sad. Github is making the files executable
for some reason, and Nose skips executable files by default to avoid
any potential side-effects (e.g. a script that does its thing at
module level would then "run" when imported.) From Nose's --exe option
in the help:
Look for tests in python modules that are executable. Normal
behavior is to exclude executable modules, since they may not be
import-safe [NOSE_INCLUDE_EXE]
So, if you tack on a '--exe' to a manual nosetests call, it will run
the tests :) this works for me.
I'll have to add a note about this to the docs, or *maybe* update "fab
test" to look for this situation and add the --exe flag for you. Feels
vaguely unsafe, but I would hope I'd never write an executable script
that does bad things just when imported, so...
-Jeff
On Thu, Sep 24, 2009 at 10:21 PM, John Joseph Bachir
<[email protected]> wrote:
> On Thu, Sep 24, 2009 at 9:00 PM, Jeff Forcier <[email protected]> wrote:
>>
>> You're using the builtin Python?
>
> Yes.
>
>> How'd you install
>> nose and the other packages, via easy_install?
>
> Yes, OS X's.
>
>>
>> Are you using virtualenv?
>
> I don't know what that is :)
>
>> Can you send me the output of "nosetests --verbosity=5" (run from the
>> project root)?
>
> Attached.
>
>> If the
>> verbosity output doesn't give us a clue I'll probably take this
>> off-list until we find a solution, no point gunking up everyone else's
>> inboxes.
>
> Agreed.
> John
> _______________________________________________
> Fab-user mailing list
> [email protected]
> http://lists.nongnu.org/mailman/listinfo/fab-user
>
>
_______________________________________________
Fab-user mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/fab-user
