On Sun, 20 May 2007 21:12:49 +0300 (EEST) Martynas Venckus <[EMAIL PROTECTED]> wrote:
> > i think there is no need for this, because latest stable 3.x is > > already in ports. > > Cherrypy3 is incompatible with cherrypy2. Turbogears needs cherrypy2. yes i know, the api has changed with the major release. some questions: do you plan to port turbogears or why did we need cherrypy2? do you know the plans of the turbogears developers? will they switch turbogears to cherrypy3 in the near future? they are working on the migration (with the milestone 1.1): http://trac.turbogears.org/ticket/1181 and have a branch for it http://trac.turbogears.org/browser/branches/cp3 afaik it is not so hard to migrate existing applications to 3.x - but turbogears seems to use some very hackish cherrypy2 features, like self written filters. there are some more or less serious bugs in the 2.x branch which have been fixed in 3.x. IMHO: maybe wait with a turbogears port until they switched. > Both 2 and 3 are still maintained and stable; see > http://www.cherrypy.org/wiki/CherryPyDownload. > i know, main reason: turbogears.
