On Thu, 2006-10-05 at 20:48 +0200, Łukasz Langa wrote:
> Josh Trutwin:
> > On Mon, 02 Oct 2006 21:42:34 -0000
> > "fabiofz" <[EMAIL PROTECTED]> wrote:
> >
> >   
> >> For those interested... Just wanted to post that I've recently
> >> covered a little how-to on configuring pydev to work with django
> >> http://pydev.blogspot.com/2006/09/configuring-pydev-to-work-with-django.html
> >>     
> >
> > Thanks! - pydev is the best.
> >
> > Josh
> >   
> 
>     Yes, it is.
>     However, I use PyLint along with it and it gives me some problems. 
> The biggest issue so far is that Model classes are dynamic, and thus 
> don't have an 'objects' member. So PyLint gives errors like:
> 
> "Class 'Session' has no 'objects' member"
> 
> or "Class 'User' has no 'DoesNotExist' member"
> 
> I can work around this by putting
> 
> #pylint: disable-msg=E1101
> 
> in the block where 'objects', et al. is used. But this is somewhat 
> clumsy. Anyone's got a better solution?

If you think about, there's not really a lot you can hope to do here.
Anything that works by static analysis or even inferences is going to
have trouble with dynamically constructed objects (particularly using
custom __new__ methods and post-construction additions via Django's
signal mechanism). Not really a completely solvable problem with
languages that have runtime name bindings.

It's not really a problem with Django or pylint, just a mismatch between
their features. So blocking pylint from examining certain things is the
only way to if you want to use it that way.

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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to