=== CyberJacob is now known as CyberJacob|Away === freeflying_away is now known as freeflying === msx_ is now known as msx === CyberJacob|Away is now known as CyberJacob === freeflying is now known as freeflying_away [22:23] hazmat: ping [22:24] lazyPower, pong.. [22:25] hazmat: i see that you've been hacking on charmhelpers. has the general workflow with charmhelpers changed in syntactic sugar? [22:40] lazyPower, state of the art is a yaml file for defining parts, and then using charm-sync-helper [22:40] lazyPower, which will copy those bits into the charm [22:41] lazyPower, most of the openstack charms use that technique, and several others as well [22:41] I did do that following along with the video tutorial. My hang up is the module importing and then referencing. I'm long-tailing my definition and I dont understand why I have to do that. [22:41] lazyPower, did not parse that last sentence [22:41] yeah i dont know how to explain this - can i gist what i'm doing and ask for feedback? [22:42] https://gist.github.com/chuckbutler/9315090 [22:42] lazyPower, sure [22:43] lazyPower, oh.. i try not to do that.. just mapping helpers to hooks/charmhelpers avoids that need [22:43] re the sys.path manipulation [22:43] ok so move the lib dir to "charmhelpers" in hooks? [22:44] lazyPower, no.. move lib/charmhelpers to hooks/charmhelpers [22:44] ah ok [22:45] lazyPower, then py hooks can just do import charmhelpers [22:45] hazmat: along that veign, my yaml would change to be: destination: hooks [22:45] lazyPower, typically python syntax to get access to a module [22:45] lazyPower, http://paste.ubuntu.com/7024543/ [22:45] right on. Thank you! [22:45] lazyPower, would be from charmhelpers.core import hookenv [22:46] this has hung me up for the last half hour, i was starting to get discouraged