DjangoBot: #django

brosner: heh, oddly enough many of those are about the guitarist :)

mysite.urls = mysite/urls.py, of course

just like mysite.settings = mysite/settings.py

standard python module referencing

thks

how can I exclude a specific object from a queryset?

.exclude() of course

Magus-: I tried that, but the resulting queryset was broken

of course.

(not of course?)

Leonidas: then you did it wrong

pastebin some code :)

Magus-: yeah, I suppose so, moment

(or you're using a query that's currently broken)

there are a few edge cases that don't work right at the moment

Magus-: http://dpaste.com/38997/

So, I try to display only series which have more than 0 public_viewable watches

The condition was too hard for a simple exlude, at least I couldn't come up with something.

.exclude(obj) is invalid, of course

you have to use kwargs like every normal filter/etc

something like .exclude(id=obj.id) would work

Magus-: the fun thing is, it does not crash. It crashes on the print

well duh, querysets aren't evalutaed until you try to get data :)

Hi, I have a Q-related question. Due to a design-issue a object has a start_date field and a start_time field, and i want to get a queryset of objs with a date/time greater than right now, the pseudocode is something like: queryset = filter(start_time__gt=now.time() AND start_date=now.date()) OR start_date__gt=now.date(), -- as i read it, Q would do the job with: filter(Q(start_time__gt=now.time

(), start_date=now.date()) | Q(start_date__gt=now.date())) but I must be mistaken because that produces faulty output... any pointers?

so you go and build the invalid one, and on the print it dies

Can someone tell me why, when I update 'reports_to' in this: http://dpaste.com/38998/, 'supervises' also updates with the exact same content?

because you didn't turn off the symmetrical option

sillyperson: try using & to combine the first two, instead of foo,bar

hrm

I'm trying to use modelforms to edit a model

how do I get it to populate the existing values of that particular object into the form?

Magus, really? I read the description of symmetricl, but it didn'tseem to apply in this case. It did work when I put it on though, but thought I might it be a bug. Guess I was just reading it wrong.

christ!!! ... Magus- you're a saint :-)

notanumber: symmetrical = what you add to one m2m is added to the other side of it

what should i do if i want to format a datetimefield in a newforms form(modemform) before outputting (i need 12.3.07 instead of 2007-3-12)? the boundfield.data just returns None - so what do i need to change?

in this case, it's likely interpreting the 2nd m2m as the other side

and any m2m to 'self' is symmetrical by default

modelform*

gordonjcp: pass in the instance.

cccp: as far as I know you cannot change the initial display of the data in the form

you could try a custom datefield and/or widget though

brosner: pass it in where?

hm :/

gordonjcp: MyModelForm(instance=obj) as the docs say

Magus, but that's still the case for two seperate m2m fields?

can i easily replace the normal widget with it? (i use a subset of the fields via a modelform)

notanumber: every m2m to 'self' is symmetrical=True

you could make 50, they'd all have that set

OK, so I need to authenticate with our AD server and mattmcc recommended a custom backend for the auth middleware. However, I need support for our AD groups as well. From what I've seen of the backend it's for user authentication only and groups are implemented as a db thing. Is there a way I can extend the Group functionality?

brosner: aha, thanks

Magus, oh. I see what what you're saying. That's an odd behaviour, isn't it? WHy would you want that.

no it isn't

brosner: next problem is that dropdowns don't work

for instance, suppose you had a userprofile with a 'friends' m2m to self

if user A is friends with B, B is friends with A

symmetrical handles the other end automatically

tada

:P

hrmm, this is going to take either more beer or more sleep to fix

gordonjcp: more info please

notanumber: but since that's not /always/ desired, the option can be disabled

Magus, that part makes sense. My case has "user" with two m2m fields: supervises & reports_to. Changing either one in a user records, changes the other. That's the part that seems odd to me.

I would have thought they'd be distinct.

notanumber: and normally they would be

I think the symmetrical is getting in the way

it may be a bug with that option, I don't know

Magus, I thought it might be a bug. Didn't see a report for it though, so thought I'd confirm.

I'm not entirely sure :)

Magus-: thanks, I got it working properly.

Symmetricl=false did fix it though.

Maybe I'll submit a bug report either way. Let the developers decide if it's a bug or not.

Magus, actually, I lied. S=symmetrical=False didn't work. Now adding a user, "Bill

, whom reports to "John". Added Both "John", & "Bill" to 'reports_to' & 'supervises' for John.

and Bill

hmm

you could try using db_table to specify different tables for each m2m

but definitely file a bug for that one

Well, at least I know I'm not going crazy. heh. Can't type for crap tonight though...

whats the best way to extend user class?

behold, the power of google

first hit

thanks magus, i went thru this post, but there are other methods, i'm asking about the best

no there aren't

what other methods?

that's the only method

check http://www.amitu.com/blog/2007/july/django-exte...

that method is absolute shit

so yah, use the b-list one

alright

lol..

yes it is lol

omg, seriously... what a shame