On Fri, 2009-03-20 at 11:38 -0400, Dan Mallinger wrote: > Thanks Malcolm. I'll try and look into this when I have a little > time. It would be nice to be able to contribute
By the way, I believe this problem really shouldn't be that hard to fix, so it isn't a bad way to start out diving into the code. I haven't personally done it as there are about 5000 other things to fix as well, all of similar priority. But if you have quick grep through the code for where app_label is used, you'll find it being computed automatically in only one (maybe two) places, from memory. Walking up a module hierarchy isn't exactly rocket surgery, either. So I guess I'm also not fixing this myself out of obstinance. If people want it, it shouldn't be that hard to write a proper patch with tests and everything and it's not something that can't be fixed by pretty much anybody with sufficient motivation (I'm happy to admit there are some enhancements and bugs that probably aren't "my very first bug fix" candidates; this isn't one of them). By all means, have at it. I think you'll find it rewarding. :-) Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
