You will need to watch that libraries/modules or code that uses things like "with" (context managers ...) include the from __future__ import with_statement otherwise these will blow up when you run in production.
Also 2.6 has advanced string formatting .format method of str and unicode which isn't present in 2.5 2.6 has a future feature of using print as a function. Here is a complete list http://docs.python.org/whatsnew/2.6.html So the bottom line is you whilst 2.6 will work in dev, you could end up with code that will not run in production. Chances are you are unlikely to use these features in your own code but a thirdparty library could. So user beware and test in live appengine (get your self a test instance) before you unleash you new code on the masses ;-) Personally I wouldn't bother using 2.6 until it is officially supported by google in production. The little extra pain you might have in dev setting it up will be a lot less than the production pain if you miss something and have to go and install 2.5 anyway ;-) Rgds Tim On Oct 6, 11:17 am, Peter Petrov <onest...@gmail.com> wrote: > On Wed, Oct 6, 2010 at 3:28 AM, Ikai Lan (Google) > <ikai.l+gro...@google.com<ikai.l%2bgro...@google.com> > > > wrote: > > - Fixed an issue with task queue tasks not running on the dev_appserver > > when > > using Python 2.6. > > Does this mean that Python 2.6 is now (more or less) supported for the > dev_appserver? Are there any significant issues remaining when not using > Python 2.5? I'm asking because it's quite a pain having to setup an old > Python version on modern Linux distros. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
