what breaks going from 2.3 to 2.4 ? just curious. On Jun 28, 2006, at 7:10 PM, William K. Volkman wrote:
> Just FYI, > On Wed, 2006-06-28 at 16:41, Michael Bayer wrote: >> or you could get your ISP to install python 2.4. 2.2 has some >> stability issues with weakrefs (which SA uses). > > Moving our application from 2.2 to 2.3 was painless. Going > to 2.4 was/is another matter. Three months have been spent > and the task is not yet completed at this time (just in time > for 2.5, yea! :-P). > > The (b)leeding edge is not so wonderful when you have multiple > systems that interact and must work together smoothly and > reliably. Module "foo" provides capability to acquisition > and to back-end processing. Acquisition is a 24x7x365 > .999999 uptime system. Through the magic of reload(foo) > you can keep capability constant as well as fix bugs. > Module foo requires changes to work on 2.4, if you fork > "foo" you have the problem of keeping functionality on par, > destroying all your hard refactoring and code re-use. > > I'm not advocating holding back, however there is something > to be said for not breaking backward compatibility. It > once was a priority for python, the glamor of feature > creep seems to have snuck in and stolen it away. > > YMMV, > William. > -- > William Volkman - Zmax Solutions Inc - http://www.zmaxsolutions.com > 7222 Commerce Center Drive, Suite 250 - Colorado Springs, CO 80919 > Phone: 719-594-2060 x202 Fax: 719-594-9003 Cell: 719-330-8423 > Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
