DjangoBot: #django

try the "new" module... standard python module

or there's getattr and globals

FunkyBob: eval method doesn't require importing any extra code - but yes it's ugly :)

new.classobj(str) ?

Q45: why do you have the object name in a string?

i've got something where i have a class with several descendants, and i need to decide which descendant to use

something like the factory pattern

jinzo: I meant upon ModelForm.save, not when populating the ModelForm itself

I can see how you wouldn't want ModelForm to always fill in the current user, but it seems much more likely to me that you would want that behavior, so perhaps a toggle defaulting to true

Kilarney: because the current user is tied to a request, and a form isn't

ahh, true

Q45 getattr(module_name, class_name)

er, that should be module, not module_name

what if it's in the current module? use __main__?

globals() or locals(), depending on the scope

Q45 dont' do it in the current module, or use an explicit dictionary in which to look up eligible classes.

"__main__" is a name, not a module

(sorry if I confused that issue above)

yeah... I prefer to create an explicit mapping dict

it's simpler, safer, and clearer

or a separate module. Either way creates a contained namespace

mapping dict = {'Object': Object} ?

yep

then you can do foo = mapping_dict.get( mystring, DefaultObject)

is there a way to get a list of all of the subclasses of a class that have been defined?

probably

you dig deep enough, you can find anything :P

but you need to know where to dig

Q45 YourClass.__subclasses__

sweet

hmm tried it, didn't work

ah, everything has to descend from object

yes, ultimately

right

ok, this does exactly what i need

I understand that django under DEBUG mode keeps a copy of all queries made. However looking at the total of these queries I get an obvious different running total depending on what view I'm looking at. Does django retain these per view or app?

stp2007 per request, most likely

Zalamander, that makes sense. my code needs some review to explain why my query count rises in a view. hmm.

stp2007: there's some nice snippets on django snippets to give you a dump of queries (and their execution time) for a view