DjangoBot: #django-dev

No worries - it's a fine point.

Gulopine: where?

if a model contains "class Meta(object):" you'll find nice errors about invalid meta options

ew

the was class Admin: but i don't actually know for sure if that's true or not

and that's going away "soon" anyway

i can file a bug if you like, but i hadn't bothered because the docs all show old-style classes

that's not really a big deal, though, since that class gets swizzled into an Options instance.

But it wouldn't be a bad idea to fix it just in case someone wants to be all propper :)

it does get a little annoying in my dynamic model examples though

since i can't use type() to create an old-style class :)

Probably whatever's breaking there is gonna break on 3k too, so worth figuring out what the deal is.

Won't that be an issue in 3.0 once newstyle is implicit?

Alex_Gaynor: Jinx

it's a simple fix, really

just two extra lines

i'd be happy to file it

Yup, make it so.

the joys of writing a book about all these internals

i should actually make a list of all the bugs i've filed as a result of the book

so far it's just a handful, but it's still early :)

Then you can write the sequel about fixing them

I almost wrote that SQL :P

they're already fixed :)

hrm, although ... how robust do you want it? :)

just in case python3k adds more __*__ attributes to classes, i mean

You're talking about validating the fields that are allowed in Meta?

yeah

i was just gonna add in checks for __dict__ and __weakref__, but if there might be more later, maybe it's worth future-proofing

We could have Meta inherit something and just use __slots__

...

Alex_Gaynor: that would require changing how people declare it, so, no.

Gulopine: just let anything _* slide.

I know, I was just presenting the option :D

oh, okay

that's easy enough

i was gonna leave it at __*__

nah, _* is private enough :)

true

should those be just ignored entirely, or be tacked onto _meta?

(reaching too far)

nvm

just ignore for now, but I can read your mind: I totally want a mechanism for allowing custom stuff in _meta, too :)

hehe

you know me so well :)

thus far, i appreciate the idiot-proofing though

yay 4 bug hunting

ah, and besides

the stuff with str + unicode_subclass calling __radd__ of unicode_subclass is against official spec

I don't really care, just telling

fijal: where's that?

jacobkm: safestring

or auto-escape string

something like that