Define tasks implicitly

[andreif]

Hey, got similar idea and the name 😂 Great that you started working on it. I had a slightly different thing in mind. Say you install it system-wide and don't require importing anything. Could be an alternative way to use your tool. One just needs to find a way to distinguish functions defined in Pykefile from potentially imported ones. Maybe naming convention could help, e.g. task_... and/or ..._task. Or would it be too implicit?

[frissyn]

@andreif Thanks for your interest in the project, though I'll admit I forgot about it for a long time :3

Your idea is definitely plausible, and would make the end-user experience much nicer, since having Python functions end in _task is a nice organizational convention.

The problem then is how to provide utilities like pyke.export or pyke.shell. I guess I could drop those? Seems more trouble than it's worth to remove the import, but I'll take some time to re-visit the project when I'm less busy, thanks!