Re: @cache_control() and @never_cache not working

In that version (0.96) of Django was bug in combination of these decorators and CacheMiddleware. If you can use upstream version then everything will be working. Otherwise look for these (closed) tickets on http://code.djangoproject.com and patch your version. Tomas Kopecek

Re: Internationalization

db > and add it to the .po file? > How can I do it? > Thank you. > > In this case could be usable gettext_noop() function for menu items. -- Tomas Kopecek e-mail: permonik at mesias.brnonet.cz

random seed with multiple processes

_after_ forking? Or do we have to wait for desynchronizing threads by user? -- Tomas Kopecek e-mail: permonik at mesias.brnonet.cz ICQ: 114483784 --~--~-~--~~~---~--~~ You received this message

Caching binary data

are not instance of text string. -- Tomas Kopecek e-mail: permonik at mesias.brnonet.cz ICQ: 114483784 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: Django Browser Games?

translation but no support) and after evaluating phase it will probably go international (cz,sk,pl,en). -- Tomas Kopecek e-mail: permonik at mesias.brnonet.cz ICQ: 114483784

Re: Random objects in view

Alessandro Ronchi napsal(a): > 2007/10/1, Tomas Kopecek <[EMAIL PROTECTED]>: > >> Now, I don't understand. What is the difference between these two cases? > > I don't know. If I put the random order before filter it works, if I > put it after filter it doesn't. >

Re: Random objects in view

Alessandro Ronchi napsal(a): > 2007/10/1, Tomas Kopecek <[EMAIL PROTECTED]>: > >> items = shuffle(items) > > > If I do that I get > > Exception Type: TypeError > Exception Value:object doesn't support item assignment > Oh, sorry, I forget th

Re: Random objects in view

e this from random import shuffle items = shuffle(items) -- Tomas Kopecek e-mail: permonik at mesias.brnonet.cz ICQ: 114483784 --~--~-~--~~~---~--~~ You received this message because you ar

Re: Incrementing in django templates

eed this case (indexing for cycle), then use variable {{forloop.counter}}. Otherwise you need to create new template tag. -- Tomas Kopecek e-mail: permonik at mesias.brnonet.cz ICQ: 114483784 --~--~-~--~~-

Re: QuerySet & memory

ing to some other DBMS or to use explicit slicing. For me it could be more appropriate to change iterator() to do some slicing for me (by explicit LIMIT clause), maybe a small patch for our application. I understand, that changing it in general would be a bad design decision. So

QuerySet & memory

and enumerating objects? Is there any way to load object on demand only, so to use memory only roughly equal to sizeof(SomeModel)? -- Tomas Kopecek e-mail: permonik at mesias.brnonet.cz ICQ: 114483784

Re: ugettext vs. ugettext_lazy

cial. I've should thought about it. Now it makes much more sense. Everytime I've played with ugettext* I've used it inside functions and so I didn't noticed this behaviour and everything looked same for both of them. Maybe, it should be mentioned in documentation also. --

ugettext vs. ugettext_lazy

must be completely missing something important in this area. Can anybody enlighten me, please? -- Tomas Kopecek e-mail: permonik at mesias.brnonet.cz ICQ: 114483784 --~--~-~--~~~---~--~~ You

Re: Template tag and combining variables & text

Emanuele Pucciarelli napsal(a): > > Il giorno 29/lug/07, alle ore 22:48, Tomas Kopecek ha scritto: > >> I know, it's syntactical nonsense. But does anybody know about some >> way >> how to combine variable content with string content? Is it possible? >> >

Template tag and combining variables & text

ndimg %} -- Tomas Kopecek e-mail: permonik at mesias.brnonet.cz ICQ: 114483784 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this gr

Re: Cross-refering models across files

Tomas Kopecek napsal(a): > Tim Chase napsal(a): > I> does anybody knows, how to implement cross-refering models across files? >> # in example_app/models_a.py >> class A(models.Model): >> # no ref_to_b here >> ... >> >> # in examp

Re: Cross-refering models across files

ne-to-one relationships will be changing soon, so we don't recommend you use them." Maybe this is more question for django-devel... -- Tomas Kopecek e-mail: permonik at mesias.brnonet.cz ICQ: 114483784 --~--~--

Cross-refering models across files

djago.db.core.options which coredumps in point where it wants to load some data from (not yet defined) class B. Is there any general technique to workaround this behaviour, or it is completely problem of model design? Thanks for some future response. -- Tomas Kopecek