DjangoBot: #django-dev

jezdez, did you get some time to think about #7239 ?

Willison Consulting: "Yes, we have no nodes today!"

jezdez: oh I'm totally +1 on that

oops

david`bgk: I'm +1 on #7239

SimonW: i have some legacy code that puts everything under one tree with mptt so i lucked out with just being able to sort by lft ;)

hmm.. hadn't thought of that, I could always give everything the same root node as a workaround

telenieko: jacobkm: care for a look at #7239?

jezdez, great :)

SimonW, did you use the "official" oauth lib for your work with OAuth?

david`bgk: I used it for wikinear.com

the official Python one

I'm suprised that there is no django-oauth

ok

it seems that tests are broken

I've only done OAuth consuming, haven't built an OAuth providing API yet

there's nothing django-specific about consuming, but yes an oauth providing Django project could be neat

I'll try to make an independent app for the provider part

there's a django fireeagle thing which is pretty neat

While I'm in here, I'll mention that a simple patch to #7197 and #7353 seems to fix unique_together which was broken on trunk as of a few days ago. I don't know if the change has any nasty side effects or not though.

OK, I'll take a look at that but that's the provider part which is interesting for me

empty: one thing of the bouncer is that I now have a shiny hostname ;)

telenieko: well your use case makes sense.

yep, it's nicer than my isp's hostname ;)

Hrm, when are we planning to commit #285 ?(Is that patch even up to date)

Alex_Gaynor: before 1.0; the patch isn't up-to-date but the basic idea is pretty simple. It's just backwards-incompatible for anyone running Django anywhere except /, so it's going to be annoying.

Ah, ok, I was just wondering if we were going to wait until last minute to avoid backwards incompatiblity for anything except the 1.0 release(ie no trunk breakage), or as soon as possible for more testing

Actually now that I think about it, it's clearly going to happen within the next few weeks since it's a 1.a task

I'll probably aim to do it during the pre-alpha sprint; that'll introduce a few other backwards-incompatibilties -- newforms-admin! -- so people can do 'em all at once.

Which reminds me, I need to make a blog post about upcoming changes at some point.... hrmph.

Big Changes; FYI 1.0 is coming

Exactly.

Actually, this patch isn't as out-of-date as I'd though. Just a couple of conflicts. Cool.