Hi,
I'm not sure about your exact problem, but I solved similar competing Django
version issues by adding the following at the top of main.py:
for k in [k for k in sys.modules if k.startswith('django')]:
del sys.modules[k]
-Chris
On Fri, Jul 23, 2010 at 7:42 AM, Blixt <andreasbl...@gmail.com> wrote:
> This issue seems to occur if using the Admin console (which I use to
> execute arbitrary code on live data), and a new instance is started
> (thus loading Django 0.96 before my code gets a chance to load 1.1).
> Is the only solution to not use the Admin console, and instead use
> some kind of remote datastore solution?
>
> Oh and by Admin console I mean I have added this line to my app.yaml:
>
> - url: /admin/.*
> script: $PYTHON_LIB/google/appengine/ext/admin
> login: admin
>
> --
> 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<google-appengine%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>
--
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.
