Matt Robenolt

We can either just expand the search path to effectively match root, or we can just do a custom Loader that works based on relative from where it's being executed...

No worries, I haven't looked at that care, but it doesn't particularly matter. My code is explicitly disallowing it because in most normal uses of Jinja, this is correct/secure behavior....

Yeah, this is great! Thank you!

Hmm, seems like it would be an easy fix. I can try to whip something up, but if in the meantime you wanted to submit a fix, I'd happily review...

meh, that's not a right fix.

Sorry for the delay, I'm going to look over this today, but this looks good!

I think it was just waiting on some outside confirmation. Wanna try it out? :)

What's the usecase for this? I get what it's doing, I just can't think of why I'd want to use this.

I'm going to probably pull this in later. Do you have a preference on it being a CLI argument? To be, it seems like we could just allow this behavior...

I may be a little disconnected here, but why not replace `pip` with an alias that was effectively something like: ``` alias pip=/usr/bin/env python -m pip ``` Or a script...