#django

Kedgen: you're doing a few things wrong :) for one thing, your CBVs, which is what django-braces works on, need to be classes. So they'd be defined with `class` not `def.

Kedgen: secondly, if you want a list of model objects, why not use a ListView instead of a TemplateViewL

s/L/?

__love__: Ah yes, that all makes sense :) Thanks!

Kedgen: if you're still learning views, in general, i'd suggest sticking with function-based views and using the @login_required decorator

__love__: +1e6

?

__love__: am conveying my support for your statement

haha

what do i get if I try request.user in a view and there is no user logged in? Is it just blank? Basically, before I execute commands in a view, I want to make sure the user is logged in.

__love__: it's troubling to me that people new to Django are somehow getting the impression "You should try to use CBVs for everything" ... or, at the very least , "You should use CBVs by preference"

velcrow: it'll be an AnonymousUser

__love__: for a short time there, we even got people who were convinced that function-based views were going away, totally supplanted by CBV

FunkyBob: well, you SHOULD use CBVs by preference ;) they're better in most cases (at least IMO). but, yeah, it's funny that so many are jumping straight to them

so I can just do something like user = request.user ... if user == AnonymousUser ...

FunkyBob: the FBVs-are-going-away was from badly written press about the generic views

velcrow: why not just `if request.user.is_authenticated`?

__love__: yeah, I got that... and it was fixed...

How do I use F() object with queryset annotate? I was thinking qs.annotate(value=F("numerator")), but I get 'F' object has no attribute 'lookup'

velcrow: you should read the authentication docs

__love__: I disagree... you should use CBV where they fit

FunkyBob: which is most places ;)

far too often I see people doing strange contortions to their code to make them fit in a CBV

FunkyBob: we'll likely have to agree to disagree.

__love__, Oh that looks good. Yes I have read them many times but since I am new, I can't remember all the functions. Soon I'll get the hang of it.

velcrow: think of a problem, read the docs, write the code. lather, rinse, repeat :)

lol ok, thanks

velcrow: what __love__ said.. then do it again :)

FunkyBob: i'm also probably partly to blame on the "let's all use CBVs" approach, since i strongly push them in GSWD

alright :)

FunkyBob: and pydanny pushed them in 2scoops

__love__: again, I'm not _against_ their use [unlike some people]... I just think that, like all tools, they should be used where appropriate

Are F() objects usable with annotate at all? Couldn't find documentation for either way

err either way == yes or no

gp: suck it and see :)

The annotation has a field name, so yeah.

Well I get 'F' object has no attribute 'lookup', but am I doing it wrong?

__love__, The docs say that is_authenticated always returns true. I can't understand that.

is_authenticated()

Always returns True. This is a way to tell if the user has been authenticated. This does not imply any permissions, and doesn’t check if the user is active - it only indicates that the user has provided a valid username and password.

What's the point if it always returns true?

velcrow: unathenticated users are implemented by a different class

velcrow: AnonymousUser is a separate object.

how do I get the max/min possible value for a FloatField?

subleq: its is_authenticated always returns False

A User is a model, tied to a database record. So if you have a User, you automatically have an authenticated user.

I see

velcrow: read the last section of that sentence

So if I try is_authenticated on AnonymousUser, it would be false?

yes

correct

this is all covered in the auth docs

Ticket.objects.filter(pk=objid).update(flagged=objvalue)# If objvalue is "1" and flagged field is boolean, do I have to do any casting?

apollo13: hey, remember my django-rated app? finally made a release yday... as it's now being used in k3 :P

Thanks

introspectr3: almost certainly not

mindlace: That'd depend on your database. Though since FloatField is inexact, it may not be the field you want.

I am trying to use F() objects two divide two fields and then use Sum to sum the results for all matched objects. Are you saying that I should be able to do qs.annotate(value=F("numerator") / F("denominator"))? If so, what does the error about "lookup" mean?

eh, i think it's more a geodjango question since what I really am trying to do is represent a 3d coordinate space in geodjango

gp: sadly, I think not

er, just represent a cartesian 3d coordinate space

gp: but it's worth trying

FunkBob: http://pastie.org/7981756 objid exists, objvalue is correct value, im getting the httpresponse, but why isn't it updating the field?

introspectr3: oh.. mysql? all bets are off :P

lol

lol i know, switching to mongo or maria will be easy enough, its just what was on there already

MySQLOL

FunkyBob: alright thanks. I was just confused about whether the "lookup" error meant my syntax was incorrect or that the functionality is not supported

you think mongo will solve problems?

introspectr3: probably worth using a form there... would save some effort

gp: lookup error?

__love__: that depends on what your problems are

FunkyBob: immediate consistency is such a downer ;)

FunkyBob: 'F' object has no attribute 'lookup'... but it makes sense now that you said I can't do that

gp: ah, right... no, there's no Aggregate in that expression

[sorry, am being distracted by my daughter]

FunkyBob: np, thanks

So if you were going to track view counts on objects that can be both partially viewed or completely viewed would you use a FloatField or a DecimalField?

depends on the level of granularity you need

gp: If decimal accuracy is important, DecimalField.

Although if you're only dealing in, say, 1's and 0.5's, the float would probably do fine.

Well among other things it will track partial video views by byte ranges requested so the decimals could be odd. That is why I was just going to store the numerator and denominator and make the decision later with a South migration

I'm going to take a massive step back, I've never been able to get this right. formats.date_format(value, "SHORT_DATE_FORMAT")… it's always in the US format for me mm/dd/yyyy. I can't figure out for the life of me how to get it to dd/mm/yyyy

scottyob: have you played with the l10n flag?

FunkyBob: yeah, I've turned it both on and off in my settings.py file

I've tried setting DATE_FORMAT, DATE_INPUT_FORMATS, DATETIME_FORMAT and I can't for the life of me get it to show the proper format

bloody humans, why can't we just decide on standardising? :P

sigh: Ticket.objects.filter(pk=objid).update(flagged=objvalue) doesn't work when objvalue=="0", Ticket.objects.filter(pk=objid).update(flagged=0). What am I missing?

scottyob: everyone except the Yanks can choose a sensible date format ... :P

Err, it does work if I specify 0

introspectr3: well, "0" is True

you said almost certainly not!

ok, so I do have to cast from string to int?

howdy yall

having a bit of trouble with unit tests, I keep running into this issue and it's probably due to a fundamental misunderstanding somewhere. http://pastebin.com/xPgw9n9i. Receivable with id=1 is in the fixture i'm loading. The change is reflected by the ajax response, but when I test the attribute on line 8, it hasn't changed.

introspectr3: I would probably use a form with a TypedChoiceField

If "flagged" is boolean, you really ought to use actual boolean values in there.

but, yes, since the value is coming from a HTML form, you will need to do some work on it

hmm ok ty

any thoughts?