Doug Tangren

I've got some direction from these to be published docs https://github.com/rust-lang-nursery/edition-guide/pull/117/files#diff-4e57182b623c416bc83329f6a7307ec9R177. The foreign macros crowbar uses needed the `cpython::` path prefix. I'm going to experiment with this a bit more...

Oof! that worked but _using_ the lambda macro then requires the user to import all of the helper macros that cpython uses inside _its_ macros. I'm going to see if...

wanted to leave an update on this as I'm still keeping an eye on the cpython issue. still no progress towards using the 1.30.0 stable form of `$crate::/local_inner_macros` as an...

Nice. That may end out being a safer bet. I'm getting the impression cpython crate is not very _actively_ maintained. That makes it harder for crates like this to evolve...

Got some feed back from the cpython crew that is [not actively maintained any more](https://github.com/dgrunwald/rust-cpython/issues/159#issuecomment-435079176) :/ which means it may be behooving to start casting a closer look at `pyo3`....

I think this is fine as is I've been using lazy static and thread local https://github.com/meetup/pulley/blob/master/src/lib.rs#L67 In general it's best to initialize expensive ops like this for performance in lambda....

If you're looking to cut a new release I've got one change I'd like to get in. An setup ergonomic issue I recently solved for lando, an extension of crowbar...

I'll try to follow up with a crowbar pull today and you can let me know what you think

Im actually going to open a new issue on this one realizing the context is going to get lost in an unrelated thread :)

carrying on over here https://github.com/ilianaw/rust-crowbar/issues/45