On Sat, 2010-09-25 at 09:27 -0700, Ben Bangert wrote: > On Sep 25, 2010, at 4:43 AM, Santhosh wrote: > > > I checked the new developing version of pylons .The new version is > > entirely different from the older version . How can the developers > > follow this ? .The developers compelled to have change the developed > > software because if they remain in the older version there may be have > > no support . > > I don't understand what you mean by "How can the developers follow this?". I > posted the entire thread here to try and help any other developers follow it. > > It's quite different, because the current Pylons 1.0 implementation is more > or less "frozen", the implementation of most of it can't be changed since so > much of it was directly subclassed by developers in their own apps. This > style of customization was useful, but led to practical limitations on > extensibility, and our own ability to move Pylons forward. Rather than > re-inventing a bunch of code all over again, this new version went forward to > build on other code to allow the new Pylons to be substantially more > extensible, more efficient, and not have developers subclassing objects from > Pylons (which limits our ability to make changes to the framework). > > I don't see what the worry is about remaining on the older version, the > Pylons book and the documentation is not going anywhere. The same level of > documentation support is going to remain available for Pylons 1.0, as there > is a large installed base that most likely isn't transitioning all that > quickly. There is no book for the new Pylons paradigms yet, so you'll see a > much higher level of 'support' in the way of blog postings, and documentation > for 1.0 for some time to come I believe.
The trunk is also currently entirely bw compatible with Pylons 1.0. You don't *need* to use the new features. -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
