Hi, Sorry for not responding sooner that we were working on the fix before you discovered that we pushed out the fix :)
-Marzia On Fri, Feb 3, 2012 at 1:22 PM, Cezary Wagner <[email protected]>wrote: > Looks that works now both - checked on test application - both dirs > contains django! > > D 2012-02-03 20:46:40.385 /base/python_runtime/python_lib/versions/ > third_party/django-1.2 > D 2012-02-03 20:46:40.385 ['django'] > D 2012-02-03 20:46:40.385 /base/python_runtime/python_lib/versions/ > third_party/django-1.3 > D 2012-02-03 20:46:40.386 ['django'] > > On Feb 3, 6:41 pm, Cezary Wagner <[email protected]> wrote: > > Still not have idea why in 2.5 python on server there is not django in > > library directory - why path set by use_library is empty? > > > > On Feb 2, 6:37 pm, Cezary Wagner <[email protected]> wrote: > > > > > > > > > > > > > > > > > Hi I found that there is notDjango1.3on servers since path is empty > > > - how it passed tests with such bug??? > > > > >http://code.google.com/p/googleappengine/issues/detail?id=6847&sort=-. > .. > > > > > In case olddjangoeverything is o.k. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
