Re: Revisit Django trunk and Python 2.6

I had no prob. running trunk on Py2.6. I ended up going back to Py 2.5 because the Google App Engine environment is still running 2.5 (that's where my latest app is going). See... http://code.google.com/p/googleappengine/issues/detail?id=1159 K On May 24, 12:21 am, Kegan

Re: Revisit Django trunk and Python 2.6

If you need to use mysqldb, you may have problems. At least, I ran into snags last time I tried to use Django trunk with mysqldb and Python 2.6, and dropped back to 2.5.x --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google

Re: Revisit Django trunk and Python 2.6

Thanks! Time for the switch. On May 25, 2:09 am, Skylar Saveland wrote: > On May 24, 3:21 am, Kegan wrote: > > > I am always using Django trunk and Python 2.5.4. And having no > > problem. > > > I am thinking of switching to Python 2.6 (just to use

Re: Revisit Django trunk and Python 2.6

On May 24, 3:21 am, Kegan wrote: > I am always using Django trunk and Python 2.5.4. And having no > problem. > > I am thinking of switching to Python 2.6 (just to use latest python > version). Anyone is already doing this in development? production? Any > problem? > > Thanks.

Re: Revisit Django trunk and Python 2.6

On Sun, May 24, 2009 at 2:21 AM, Kegan wrote: > > I am always using Django trunk and Python 2.5.4. And having no > problem. > > I am thinking of switching to Python 2.6 (just to use latest python > version). Anyone is already doing this in development? production? Any >

Revisit Django trunk and Python 2.6

I am always using Django trunk and Python 2.5.4. And having no problem. I am thinking of switching to Python 2.6 (just to use latest python version). Anyone is already doing this in development? production? Any problem? Thanks. --~--~-~--~~~---~--~~ You received