#django

rakl: Not enough to worry about.

awesome, thanks

FunkyBob, is not enough if i return json data to backbone.js to backbone work with django?

to make backbone work with django

molavy: more or less, yeah

tastypie affect whole project , FunkyBob, all models and url need resources

no

I am writing a light-weight JSON API tool... but it's not quite ready yet

I've got a series of statements in a view that set a value of an existing object only if a value on the form was specified. Given the following sequence, is there a better (dry) way of doing this? http://pastebin.com/dm25R9gH

martian: something like that: http://dpaste.org/oRWtY/ ?

hey guys, is there any pastebin I can use to demonstrate a django app that's misbehaving?

Gambit-: like the one mentionned by the chan topic ?

ah it truncated

well that was a little more rudimentary than I was expecting, but okay :)

Well there's this reproduction: http://dpaste.org/QCAMw/

That's not actually reproducing exactly the problem I'm seeing on the other branch, but it still seems wrong.

django+tastypie

well, I don't really know about tastypie, but there's an irc chan for it

oy FunkyBob

http://dpaste.org/srjFD/ has the actual backtrace

it's not the actual error I ran into in my project - that's a silent failure on actually adding the equivilent of the TestTP0 model, but babysteps.

Oh Linovia yes, like that! I'm still learning to think in python :)

apollo13: ping

Linovia: pong

Linovia: that was fast, what did I break?

apollo13: nothing, and your last commit answers my question ;)

FunkyBob: is it backwards incompatible?

answered

Linovia: hehe, what was the question?

about the use of django.utils.six instead of six

ah

(for django-filter)

yeah using six as a dependency on python 2 is somewhat hard

FunkyBob, any luck?

but with the release of 1.5 django 1.3 won't get security upgrades so I just dumped it

apollo13: probably

FunkyBob: please verify and open a release blocker then

apollo13: oh, you mean the onetoonefield thing?

ye

+s

hrm

I will hate you for it but that's live

apollo13: question is... is it wrong?

FunkyBob: does it break code running on 1.4, then yes

only if that code is relying on documented behavior

I know that I always hate ForeignKeys for raising DoesNotExist, it makes sense if OneToOne does the same, but we at least have to mention it in the release notes and verify it

yes hence a ticket and a testcase so other core devs can verify it

ok

apollo13: looks close

36. if getattr(obj, 'author', 'None') is 'None': <-- his code is intresting^^

FunkyBob: so according to him it already raised DoesNotExist in Django 1.4?

apollo13: heh. yeah, I noticed that too...

guess he's doing something differnt

this case was code I worked out of InheritanceManager in django-modelutils

sorru... family is heading to watch NYE fireworks

already?

9pm... for the kids

ah, ok -- if you can make a testcase that would be great, we want to ship RC asap but I guess you have time till tomorrow ;)

don't get shot!

yep, will do

(/me hates fireworks in combination with stupid people shooting them :( )

hi

i'm having a hell of a time with a urls.py config. " r'^(?P<slug>[a-zA-Z0-9-]+)/dashboard/' keeps resolving to r'^(?P<slug>[a-zA-Z0-9-]+)/$

I have some app in dango, that uses __repr__ method of User while debugging and logging, but when user is retreived from request object is wrapper with SimpleLazyObject. This object does not pass __repr__, you think it should? I monkey-patch it to return somethink like <SimpleLazyObject: %r> but I am not sure I should make a ticket for that (with a patch) or it is intendet to not call _wrapped.__repr__. Please tell me whether I should make a t

spinus: why don't you use the __unicode__ method ?

@Linovia: I am using __unicode__ for rendering user content for models (I hope it is the correct way) and __repr__ to use it for internal use, for example __unicode__ tells me someuser@somedomain.com and __repr__ tells me <User: pk:2 email:something poins:100> - something which is usefull in logs, and while logging I use %r and in user content I use %s.

I see

this being said, I'm not surprised the SimpleLazyObject doesn't pass the __repr__ since it'll represent the SimpleLazyObject :)

@Linovia: but you think it sould? I just wanted to make sure this will be 'usefull' before I make a ticket.

anyone familiar with pagination in django?

@skandocious: a little

hey there! how can i tell my django model that field1 and field2 are required, but only one of them must be set?

what happens if the ordering of my objects changes between fetching new pages

spinus:

spinus: say for example I'm paginating by 3, and on the load of page 1 my objects are ordered: a,b,c,d,e,f,g,h,i <-- 3 pages worth

but between they fetch page 2, object d gets updated, and it pushes it to the top of my ordering --> d,a,b,c,e,f,g,h,i