On Fri, Jul 17, 2009 at 5:24 PM, Iain Duncan<[email protected]> wrote: >> What we need now is people with marketing skills who are not >> Pylons developers (thus not distracted by development). If you'd like >> to do marketing, you can discuss your ideas here or on pylons-devel. > > I would be interested in doing some help in this area, but it's sort of > contingent on how the whole cooperating with repoze/pypes stuff happens. > If I can feel confident that working with Pylons and repoze is going to > be a solid path forward for our company, I'm willing to pitch in there, > but not so much if I'm not sure about the future. > > Sooo, it would be good for these sorts of things if more work was put > into the public face of the future road map. On the last thread my last > questions just never got answered.... :/
Pylons 1.0 and Pypes are two different frameworks. Pylons will remain essentially as is, with some minor changes at the periphery. I've listed them on the Roadmap (updated 6/26): http://wiki.pylonshq.com/display/pylonscommunity/Pylons+Roadmap+to+1.0 The marketing issue is regarding that framework. Regarding Pypes, you must have seen Chris McDonough's message on the pypefitters-discuss list this week. He released a prototype that runs the Pylons QuickWiki demo and some BFG-like applications. Framework front-ends (called "flavors") attach to Pypes via WebOb Request/Response. I have not run the code yet but the description looks promising. If enough Pypes users try the prototype and agree this is the direction they want to go, the Pylons-ish flavor could be completed. Regarding your questions and your company, forgive me for not remembering which questions remain unanswered. You might want to re-raise them in the original thread. The main advantages of Pypes over Pylons in my mind is an increasing ability to nest mini-applications, greater modularity, and a move away from the magic globals. (However, the Pylons-ish layer will reintroduce the globals because they're an expected part of Pylons.) So that gives you two potential paths. Remain with Pylons or transition to Pypes when it's ready. My company has a few Pylons apps in production and I've trained several developers in it, so even though I personally like Pypes, we would not be able to transition to it right away. The benefits would have to be weighed against the burden of another major change. After Pylons 1.0, it will continue to be supported with bugfixes, but there may be less enthusiasm to add features if Pypes is viable by then. That is not necessarily bad because a "finished" framework doesn't need changes; it just needs to sit there and be used. There are no plans at this point that would necessitate a "Pylons 2.0". "If I can feel confident that working with Pylons and repoze is going to be a solid path forward for our company" can be read in two ways. (1) "I like Pylons as-is and I don't want the developers to abandon it for some fancy new kid on the block.", or (2) "Pylons has significant flaws that affect our company's ability to use it, and Pypes looks like it will address these problems." If the fist is true, note that the developers will have to support Pylons because they have apps depending on it. If the second is true, I assume the problem is application nesting, which has also been discussed here over the past three weeks. Pylons-dev has some code changes and application-template changes that should make nesting easier, by not depending on the magic globals in environment.py. The greater issue of "How do I plug in a bundle of templates+controller+routes without chaining to a separate WSGI application?" is, I suspect, not solveable without unacceptable changes to Pylons' structure, so it would have to be focused on a new framework such as Pypes. -- 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 -~----------~----~----~----~------~----~------~--~---
