Support module.* to include all functions in a module

[anandology]

This should follow the python import conventions like __all__ etc..

[palnabarun]

Why do we need it? @anandology

[anandology]

I have ten functions in a module and I don't want enumerate each one of them to run it as a service and change the server scripts when a new function is added.

…

On Jul 30, 2017 12:39 PM, "Nabarun Pal" ***@***.***> wrote: Why do we need it? @anandology <https://github.com/anandology> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#40 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAdkQxgYP0l_pa8pJKpfuUbFYFXIV54ks5sTCwtgaJpZM4Oi5Di> .

[palnabarun]

Oh okay. Now I get it.

So should the user do something like this?

$ firefly funcs.*

But then the user should also define __all__ in their module.

[anandology]

On Mon, Jul 31, 2017 at 6:44 AM, Nabarun Pal ***@***.***> wrote: Oh okay. Now I get it. So should the user do something like this? $ firefly funcs.* But then the user should also define __all__ in their module.

Not necessarily. If defined, then it should use all those functions. If not take all the function that do not start with an _.