Sorry I'm so late suggesting this, but... Do people have a desire/see a need for a way to make Pylint or PyChecker handle Django code more robustly? Because so many of the attributes of Django model and form objects are given as class objects or are auto-generated in instance creation, using a static checker on Django code is a mess.
Would a good GSoC project involve modifying one or both of the standard Python code checkers so that they're smarter about Django? Or maybe everybody thinks static checking is for wimps and I should just stop misspelling things... Todd P.S. I'm not a student, but I teach students who might be interested in applying. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
