Conflict with @step decorator about behave HOT 8 CLOSED

It seems like, for the sake of avoiding preventable errors like the above, it might be sensible for us to check for the decorated function's name and prevent the decoration of one called "step" (for the "step" decorator, and similar checks for the other decorators.)

from behave.

Sorry quantoid, I didn't actually give you useful advice. You will need to either use one of the other step function decorators (@given, @when, etc.) or rename your function so it's not called "step".

from behave.

Thanks, I figured that the actual function name doesn't matter so I should just call it "doit()" or something. Just something that perhaps should be pointed out in the tutorial.

Also a bit annoying that PyDev (in Eclipse) warns about the undefined decorators because they're dynamically added to globals rather than statically declared. But that's more a problem with PyDev than Behave.

from behave.

On 31 July 2012 11:28, quantoid
[email protected]
wrote:

Also a bit annoying that PyDev (in Eclipse) warns about the undefined decorators because they're dynamically added to globals rather than statically declared. But that's more a problem with PyDev than Behave.

If you want to make PyDev happy you may import the decorators into
your code with "from behave import step" (or any of the other
decorator names)

from behave.

That would be nice, but Eclipse says "unresolved import" because they're not declared in the behave module, they're dynamically added to globals.

from behave.

On 31 July 2012 13:48, quantoid
[email protected]
wrote:

That would be nice, but Eclipse says "unresolved import" because they're not declared in the behave module, they're dynamically added to globals.

Eclipse r dumb then :-) [seriously, the names are declared in the
behave package all - that should be enough for it to be happy with

• file a bug report against them ;-)]

from behave.

Yeah, but all is only assigned when the code runs, and Eclipse/PyDev doesn't run the code, it just does static analysis, e.g. looking for def declarations. Why not put the decorators in module scope rather than global? And declare them with def since there's only four? Probably a dumb question.

from behave.

On 31 July 2012 19:17, quantoid
[email protected]
wrote:

Yeah, but all is only assigned when the code runs, and Eclipse/PyDev doesn't run the code, it just does static analysis, e.g. looking for def declarations. Why not put the decorators in module scope rather than global? And declare them with def since there's only four? Probably a dumb question.

Global scopes belong to modules; that is, the module scope and global
scope are the same thing.

from behave.