Comment 10 for bug 408878

Revision history for this message
James Westby (james-w) wrote :

<james_w> kees: geser has pointed out that as we already have two copies of oauth.py in main, does promoting it cause us a real issue, even if we may not want python-oauth in main by release in its current state
<kees> james_w: given the embeddedness, I think it makes sense to promote it as-is. we should re-address it in the future, though.
<james_w> thanks
<james_w> I will continue to track the issue so that we have one copy of oauth functionality with no known gaping holes in main by release

Promoting based on this.

Thanks,

James