On Wed, Apr 29, 2009 at 12:43 AM, Robert Toscano <<email address hidden>
> wrote:
> So would the upgrade to cherrypy 3.1.x be something that would happen
> Karmic or submitted to the debian repositories? I definitely understand
> about the patch not making it into SRU.
Yes, package will be automatically synced with version from debian unstable
(3.1.1-2 at the moment) during KK development cycle.
> I think it would be silly if I combed the codebase for python 2.6
> incompatibilities, especially since that's what the cherrypy guys did in
> their latest release (don't want to duplicate work). I think your
> rebuilding solution is good for now. Thanks for looking into it.
>
>
> --
> current version not compatible with python 2.6 (Jaunty)
> https://bugs.launchpad.net/bugs/368855
> You received this bug notification because you are a direct subscriber
> of the bug.
>
On Wed, Apr 29, 2009 at 12:43 AM, Robert Toscano <<email address hidden>
> wrote:
> So would the upgrade to cherrypy 3.1.x be something that would happen
> Karmic or submitted to the debian repositories? I definitely understand
> about the patch not making it into SRU.
Yes, package will be automatically synced with version from debian unstable
(3.1.1-2 at the moment) during KK development cycle.
> I think it would be silly if I combed the codebase for python 2.6
> incompatibilities, especially since that's what the cherrypy guys did in
> their latest release (don't want to duplicate work). I think your
> rebuilding solution is good for now. Thanks for looking into it.
>
> /bugs.launchpad .net/bugs/ 368855
> --
> current version not compatible with python 2.6 (Jaunty)
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>