On Fri, Jul 23, 2010 at 11:37 PM, aliko <[email protected]> wrote: > I started reading pylonsbook but it appears outdated and there are > things that not works with pylons 1.0 any more. It seems that pylons > moves too quickly to be in time with it even minor version changes can > turn things upside down.
Pylons has been moving quickly to get 1.0 finished. Now it should move more slowly. There is a 1.1 planned but I don't know its schedule. > I've tried to install BlastOff template but it don't work with pylons > 1.0 nor toscawidjets do. In toscawidgets tw\mods\pylonshf.py file it > tryes to import things that are not works with pylons 1.0. I'm sorry if these things are out of sync. But since they're not part of Pylons or its dependencies, we can't take responsibility for them. The add-on templates have the advantage of configuring a lot of extra things for you, but they have the disadvantage of being more things that might break. You might consider ToscaWidgets, which has all these features integrated and a large team of developers working on it. > I understand that pylons is a metaframework that it is consists of > different frameworks. But each of those frameworks seems moving its own > way and with its own speed so it becomes very hard to make things > consistent through the time. Er, Paste is a metaframework. Pylons is a framework that's built from third-party components. The problem you cite is a basic vulnerability of the Pylons approach. Any library can be upgraded to provide a must-have feature, but it can also introduce bugs or compatibilities which weren't there when Pylons was released. You can mitigate this by tying your application to specific library versions; pip provides a convenient way to do this using its "requirements" feature. Of course, that doesn't help if you're a newbie installing the default Pylons, and don't know what to look for. But all Pylons' direct dependencies are careful not to introduce anything that would throw off Pylons, at least not without announcing it on the Pylons list. As for add-ons like repoze.who or toscawidgets, we have no control over those. But if you stick with ones that are also used by TurboGears, they have a large team of developers who can help with any compatibility problems. You might also want to consider using TurboGears itself, because it integrates them all together in a tested way. > Could anyone suggest me how to live in Pylons world? The best way is to ask questions about any specific problems you encounter. Read the docs at pylonshq.com, and search for your question at groups.google.com/groups/pylons-discuss -- it may have already been answered. The Pylons Book, as has been said, is out of date in some places. The Pylons wiki may also help, but some of its articles are also out of date so look at the "date modified". -- 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.
