Jonas Maurus

@LeSuisse > OK you want to use the subkeys outside of Vault. That was not how I understood what you want to achieve. Not just, but it would fit my...

@fear1226 > 1.What will be the output of create key endpoint? Will it generate a key pair ( public/private key). It will return HTTP `204` without a body, as stated...

I wish I was more famliar with golang already, then I'd take a stab at implementing it myself, but right now I am at the mercy of others :). Though...

@ionelmc hey, awesome that you're here :). Since I started work on this, I have realized that aspeclib's Python 2 and 3 code behave the same. So it seems that...

@ionelmc > * aspectlib.weave shouldn't raise any exception. If it does then you either patch the wrong way or there's a bug in aspectlib.weave. Oh man, yes, you would think...

Thanks to your advice I rewrote the weaving to happen at startup by [walking the PyGithub module tree](https://github.com/optile/ghconf/blob/03dbd5d4ffff7fdf44f90f7b4e46ecdb95e997f9/ghconf/github.py#L118). It seems to work (and obviously is much faster) and additionally removes...

> But seriously, what's wrong with the current handling? An `Advice` instance bound to a cutpoint generator function can neither inspect or modify the values that the generator returns.

To answer my own question from above: > because `hasattr(module, alias)` for a reason that I don't quite grok yet, _calls the property_. From the Python docs: > The arguments...

>> An Advice instance bound to a cutpoint generator function can neither inspect or modify the values that the generator returns. > It should be possible. Afaik I considered having...

> aspectlib.Return can't do anything else, otherwise it'd break expectations aspectlib _could_, for example, behave differently if the `Return` is yielded by the `Aspect` _before_ the caller has started consuming...