> > TG2 will still use CherryPy 3 thought correct? ( Sorry if that seems a > > stupid question from the experiment description. ) > > Well, the code produced in the sprint won't use CherryPy at all, in all > likelihood. However, as Mark said, this isn't necessarily going to turn > into TurboGears 2.0. Part of the reason that I am participating in this > sprint is because I'd like to see what a TurboGears on top of Pylons > would look like. If it looks great, and works well, there is a good > chance that I would push for it to be the beginnings of TurboGears 2.0.
Well, there's a good chance that the code we generate at the sprint will use CheryPys WSGI server, since that's the way pylons does things now. But yea, we probably won't be using very much more of CherryPy in this experimental branch. But you never know. Alberto has suggested that we just use CherryPy 3's object dispatch directly -- though that would be more attractive if CP3 had an engine-less mode. (Which it might grow later, who knows.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
