DjangoBot: #django-dev

Whenever I comment on a Django GSOC proposal I always feel like I need to preface it with an "I'm also a GSOC student, but I promise I'm not trying to sabotage you" decleration :/

freakboy3742: ping

ubernostrum: Saw your message about the blog post

I wrote one last night

freakboy3742: yes, you did.

And you let it fill in the current time.

With JavaScript.

Running on Australian time.

Ah.

Your post will go live when US Central time gets around to it.

In... 13 minutes.

Got it.

This is my breath, baited. :-)

(damn backwards yankees... :-)

hehe

bated! not baited.

No... my breath smells like small fish.

bated == reduced, like an abatement.

when is your synchronized-bomb-of-a-press-release going off?

Well, the mailing list went off last night

blog post in about 11 minutes.

ooo

cool.

I missed that in all of the hubbub recently.

Yeah, I didn't even see the mailing list post.

Was drafting a blog post of my own.

Meanwhile I still really want to wipe and lock the "stuff user in a threadlocal" wiki page.

But somebody would just create a new one.

ubernostrum: y so pessmistc?

idan: Because history has repeatedly demonstrated that this particular idea won't die.

I love being told that not everyone has the breadth of knowledge I do.

Takes a genius-level expert Django coder to come up with the idea of

def mymethod(self, user):

WHO WOULD HAVE THOUGHT OF THAT

stubborn plagues require concerted, consistent action to eradicate.

ubernostrum: I just wrote that line today, I suppose I too am a hyper expert

I'm just amazed that people don't seem to grok that threadlocal == global variable with a pretty name.

I'd say that wiping/locking the page on the wiki with a short message saying that this is a Bad Idea(tm) with a link to more relevant, modern techniques -- is a good idea.

it won't hurt, though it might not be a cureall.

freakboy3742: a thread local is worse than a global variable

You know.

freakboy3742: let's make an easter egg.

Some bit of code deep in the request handler.

Which overwrites any threadlocal named 'user' ;)

ubernostrum: :-)

With... a superuser account.

tempting...

ubernostrum: it returns your entire page rendered as a pony?

So that all those permission checks they use will always pass.

I bet I could probably sneak an obfuscated "pwn ur sitez" backdoor into the code on the wiki if I wanted to.

Also.

I want to wipe/lock all of mrts' "Django Core Specifications(TM)".

ubernostrum: Oh, please, yes.

gar. I really should go get some zzzs. Adios for real.

freakboy3742: http://code.djangoproject.com/wiki/DjangoSpecif... <-- too harsh?

ubernostrum: I'd probably change "Not affiliated" to "not part of the core team"

"not formally affiliated"

freakboy3742: fixing.

Done.

And... I'm spent.

Time for dinner, then I'll come back and look at real issues.

freakboy3742: you're live, btw.

ubernostrum: I felt the earth move :-)

Guess I should read this blog entry.

freakboy3742: I'm going to lightly edit to give people a sense of progress.

Since at PyCOn we had 300+ tickets.

ubernostrum: No probs

the indentation of the two-bullet list looks funny here

or rather the non-indentation

if I have a default argument ie def myfunc(a=_("abc")): ... will that cause problems when I use a?

like a will always be set to _("abc")

freakboy3742: edited. Mostly just providing a bit more explanation for what may/may not get bumped, and the ticket count since PyCon.

ubernostrum: Looks good to me.

malcolm's back!

:)

woot!

yay!

It's like groundhog day.

he saw his shadow?

If Malcolm sees his commit bit, two more weeks of bugfixing.

ubernostrum: two weeks of bugifixing from malcolm and 1.3 will be ready