#django

mekhami: what's wrong with the django docs?

FunkyBob: can you give me any hints on how to fix that?

FunkyBob, they're not ever as useful as guides targetting specific parts of any frame work ever?

foist: foist use a sub-select... Foo.objects.filter(pk__in=self.filter(**kwargs)).annotate(...)

it'll create a more complex query, but it'll avoid that problem

welcome to the suckage that is SQL :)

FunkyBob: thank you. I will try that.

mekhami: what is it about template blocks and inheritance you feel they're not clear about?

FunkyBob: is the db hit only once in this case?

ie, are the qs results being chained?

foist: the db will only be hit when the queryset "wave function collapses".

Oops, listening to too many science podcasts.

FunkyBob, it's usually more of a style thing than a clarity thing.. I learn better from some independent guides, things aimed at ground up learning than 'here's the documentation'. not always, but sometimes.

mekhami: what is it about template blocks and inheritance you feel they're not clear about?

foist: it's one db hit

schinckel: heh

FunkyBob, i don't see why you're asking me the same question.

anyways, i have a specific question

can i do something like Model.objects.all in a template or do I have to pass that into context

can i do db queries in the template language i guess is what i'm asking

mekhami: I'm asking you the same question, becaue you didn't answer it.

you can call any method that does not require arguments... so yes, model.objects.all will work

but model.objects.filter(..) you can not

okay.

interesting that it's not working yet..

what's not working yet?

eh i think it has to do with bootstrap more than my query

cause this looks like it should work:

idk why indentation ended up like that

did you pass Player into the context?

also, you shouldn't hard-code URLs like that...

better to use reverse() or {% url %}

okay so here's what i was getting at before

this is part of my boot strap nav bar which is in my base template

so would i have to pass Player into the context for every single view to get the base template to recognize it each time?

this is where a Context Processor becomes useful

same with the hard coded urls thing

it's a way to put a default set of information in the template context, without having to do it in every view

okay lets look into that then

so the custom processor gets defined in the view and then added to the render shortcut?

no

it gets defined in your code, added to the list in settings, and is invoked by anything that uses a RequestContext [which render does use]

defining it in the view would defeat the purpose

er

i meant in the views.py more than each specific view, but i see what you mean instead

however, you may find for your navbar it would be better to use an inclusion tag

doesn't hae to be in views.py ... I prefer to put them in context_processors.py

FunkyBob, what's the syntax for pointing to the context_processor in settings.py

like i added the defaults but do i just do something like 'standings/context_processors.py'

Any great recommendations for CI server to run on Mac OS X or Linux? Selenium support could be a plus.

hi everyone

i'm a little confused with Django Rest Framework

I'm trying to use token based authentication

i can send a request, containing username and password to api-token-auth/

and i get a token response; i also see it saved to the database

however I cant then send a subsequent request with the header: Authorization: Token XXXXXXX