#django

oh, I should finish reading the backlog before reacting

compow: depends

compow: you might want to filter the queryset and distinct it before passing it to get_object_or_404

so i would do models.Question.objects.filter(pk=question_id, pub_date__lte=timezone.now())

12 commits today...

wonder how to check how many lines i did in a day...

FunkyBob, i dont quite get it

compow: get_object_or_404 will accept a model or a queryset as first argument

get_object_or_404(Question.objects.filter(choice_set__isnull=False).distinct(), ....

okay makes sense

thanks

because when you join the m2m you end up causing multiples of the records that _do_ have choices

one for each choise

choice

but isnt that relation o2m?

one question has multiple choices but one choice doesnt belong to multiple questions

yes, but when you join the tables, you get one table of NxM rows

qs = models.Question.objects.filter(choice_set__isnull=False).distinct()

says its unable to resolve the keyword

choice__isnull=False?

choice__isnull perhaps?

okay worked

thanks

cool

the other way is Question.objects.annotate(choice_count=Count('choice')).filter(choice_count=0)

bonjello

foxo

hi, really noob question: doing a query as a listview, and returns as object_list, how can i rename that so I can use {% for project in projects %} instead of in object_list?

quite sure the docs cover how you can set that name

context_object_name ?

I'm having some trouble understanding what the docs mean about validating formsets (MAX_FORMS), example here: https://dpaste.de/mhQK

I believe by default you will have object_list and {model}_list

FunkyBob: is this close? https://docs.djangoproject.com/en/1.10/ref/clas...

wowww... thanks that was pretty easy

as it ought be, really

true, i was doing a couple other views this way return render(request, 'search.html', { 'query_string': query_string, 'posts': posts }) and didn't realize all I needed to do was set a variable

careful passing raw query strings to templates...

I believe I'm just doing it as a "you searched for..." thing, is it dangerous that way without being sanitized?

yes

from an injection standpoint?

yes

I didn't know that, thought django sanitized everything

hi all, is it possible to only change the hostname to something else than localhost in StaticLiveServerTestCase?

kmodo: well, it depends

You can put an entry in your /etc/hosts that points to localhost..

mattmcc: already have that, I would like to make tests use that domain...

that point to 127.0.0.1 (as you can't put an other name but only an ip) :)

it's set here https://github.com/django/django/blob/master/dj..., but I don't see a clean to change it

Subclass?

If it's just a class attribute.. Set it in your test.

it's dynamic and only gets created later, changing it at that point won't affect the localhost part

the hackish `self.live_server_url = self.live_server_url.replace('localhost', self.tenant1.domain_url)` does work but quite ugly :)

hmm, I'm wondering. how far I should write this cache thing myself. This is kind of a gateway proxy whateverthing which is supposed to cache external resources after some post-processing.

one thing I wonder especially is whether I should store the data in the database or as files, which can be text and binary, images I don't think past a few mibs...

who can convert it to use decorator https://dpaste.de/d8Da

I think cleaning up is simpler when I only have database rows to clear...

If it's a few mb, it'd fit in memory just fine.

yes. the piece.

but there will be quite a few requests to quite a few pieces, dunno, some 3-figure per day

Oh, you mean a few mb per image?

yup.

oh, let me check anyway

nah, it's not even mibs. it's usually not even hundreds of kilobytes. but having thousands of ~100 kib-heavy entries in a database doesn't seem right to me...

Yeah, I was thinking more like redis.

the entries expire after a few weeks.

You can set ttls on redis keys.

some at least. I don't know whether I want to add another dependency, as I have a dedicated media directory an a django app on postgres already

*that depends on

It's not exactly a difficult thing to set up.

It also makes a good option for Django's cache system anyway.

I imagine it could be added to requirements.txt, right?

No, it's not Python.

You'd install it from distro packages, like Postgres.

ugh.

apt-get install redis-server, done.

Does someone (try to) use VueJS with Django ?

I search some tips / advices on how to make them work altogether

not sure if I can mix django template and vue template or make 2 things completly seperated