Any executable from a playbook's library/ is shipped out as a single file, it seems.
This makes writing local custom modules in (say) Python a bit of a PITA: 2,000 lines of Python that conflates several cross-cutting concerns that'd be better broken out into custom modules available to import from a main utility would be much more preferable. Is there any support for doing this at the moment? Anything on the roadmap? At the moment it seems that at best I'm going to have to pre-ship my actual tools and just write a module to shim around them. Is that current practice? Cheers, jan -- [email protected] http://ioctl.org/jan/ Short, dark, ugly: pick any three OORDBMSs make me feel old; I remember when this was all fields.
