On Wed, Mar 7, 2012 at 5:50 AM, Brad Figg <email address hidden> wrote:
> Since the new version of this library broke a number of things and since
> it appears this is not going to get fixed anytime soon, why don't "we"
> just revert the changes and upload a new version for Precise?
Has it been determined that this library is the root cause, and its
not a python2.7 fallout?
On Wed, Mar 7, 2012 at 5:50 AM, Brad Figg <email address hidden> wrote:
> Since the new version of this library broke a number of things and since
> it appears this is not going to get fixed anytime soon, why don't "we"
> just revert the changes and upload a new version for Precise?
Has it been determined that this library is the root cause, and its
not a python2.7 fallout?