On Sun, 2010-11-07 at 18:16 -0500, Chris McDonough wrote: > On Sun, 2010-11-07 at 15:06 -0800, Mike Orr wrote: > > On Sun, Nov 7, 2010 at 2:48 PM, Mike Orr <sluggos...@gmail.com> wrote: > > > On Sun, Nov 7, 2010 at 2:11 PM, Marius Gedminas <mar...@gedmin.as> wrote: > > >> (I have to say that document surprised me -- pleasantly -- due to your > > >> dedication for user support. Python 2.4, even!) > > > > > > 2.4 and 2.5 combatibility will impede the switch to Python 3, as well > > > as disallowing 2.6isms which has been the current version of Python > > > for over a year. Since Pyramid is new framework, it should start at > > > Python 2.6. There can be one bridge version for existing BFG > > > applications. > > > > Actually, no. Given that Pyramid just had its first alpha, waiting > > till the second release would mean being stuck with 2.4 compatibility > > for a year or more. > > Unlikely. BFG made a major release every six months or so. > > > If people are going to have to modify their > > applications anyway for Pyramid, they might as well make them 2.6 > > compliant while they're at it. Then they'll be ready for Python 3.
And by the way, the "if people have to modify, they might as well have to modify..." argument is a little scary right now. The very time that people need stability and a clear way to do upgrades is *during* a major change like a change of import location. It's currently possible for BFG users to run a script that mostly makes their old app "just work". I don't mind adding logic to that script if it can be made to work 100% and isn't a physics research project, but I'll ask that at least for the first version, we try to let BFG users move in such a way that all they have to do is make their existing test suites pass, rather than needing to make arbitrary manual changes to both tests and application logic to make their apps work. Combining the need to do both will be a recipe in pain for them. - C -- 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.
