On Wed, Jul 14, 2010 at 1:35 PM, Guyren G Howe <[email protected]> wrote: > On Jul 14, 2010, at 13:06 , Mike Orr wrote: > >>> TurboGears incorporates Pylons. See eg: >>> http://turbogears.org/2.0/docs/main/TGandPylons.html >>> >>> So I was asking questions about what I took to be the Pylons parts of >>> TurboGears of the Pylons list. >> >> Yes, we know that TG incorporates Pylons. :) The developers sprint >> together now. What we're saying is that the parts you thought were >> Pylons are not Pylons, and since nobody has piped in to give a >> definitive answer to your questions, it means the TurboGears experts >> are apparently not reading this thread. Since it doesn't say >> "TurboGears" in the subject line, they may think it's a routine Python >> question not worth their attention. So, asking on the TurboGears list >> would get you a better answer. > > Unfortunately, I have posted several times to the TG list with no response. > I'm having issues with quite simple stuff (a simple route!), and been nearly > a week now trying to work out why it's not working. When it became apparent > that the TG list wasn't terribly helpful, I had to start looking elsewhere. > This seemed the most likely place. > > Thanks for such help as you've been able to offer.
Well, it's clearly a hybrid application because standard TurboGears apps do not have custom routes. I looked this up to confirm. http://www.turbogears.org/2.0/docs/main/RoutesIntegration.html TG uses the catcall "*url" route to send all requests to ``RootController.routes_placeholder()``, which then dispatches to the appropriate TG action. So your predecesor created a hybrid application for some unknown reason (was pure TG not enough for him? Why did he use TG in the first place then?), and who knows how many other (possibly wrong) advanced usages or unorthodoxies it may contain. So you may need to find somebody versed in Pylons, TG, and Repoze.who who can look at all the application code and figure out what it's doing and how to fix it. If you can't find a friend or fellow Python user group member willing to do it, you may have to hire a consultant. There's a list of Pylons consultants here: http://wiki.pylonshq.com/display/pylonscommunity/Pylons+jobs+and+consulting+services Either that, or evaluate whether it's worth keeping this implementation. The predecesor is gone and there are clearly questions about his code quality and lack of documentation. You may be able to write a standard Pylons program with the same functionality, and pull large chunks of the existing code into it. That would be easier to maintain and easier to get help on over the long term. Or start a new TurboGears application if you prefer, since it already has Repoze.who integration (which Pylons doesn't, although there are third-party Pylons application templates that do). Then as you copy sections into the new application, you'll see where and how it differs from a standard TG application, and you can decide whether to keep the changes or reimplement them. Plus you'll be more likely to get help from the TG list if you ask a standard TG question. -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
