On 10 avril 20:17, Dan Stromberg wrote:
> The attached 3-file shar archive demonstrates a problem I saw in a larger
> program.
>
> In short, when I use optparse (I usually do argument parsing by hand, so
> hadn't noticed until working on someone else's code) in combination with
> pylint, pylint do
The attached 3-file shar archive demonstrates a problem I saw in a larger
program.
In short, when I use optparse (I usually do argument parsing by hand, so
hadn't noticed until working on someone else's code) in combination with
pylint, pylint doesn't appear to see what attributes should exist in
On 10 avril 10:31, Torsten Marek wrote:
> On Tue, Apr 10, 2012 at 09:55, Sylvain Thénault > wrote:
>
> > On 05 avril 22:43, Wolfgang Rohdewald wrote:
> > > Hi,
> >
> > Hi,
> >
> > > I just thought I might not be the only one who would want something like
> > that:
> > >
> > > If I have statements
On Tue, Apr 10, 2012 at 09:55, Sylvain Thénault wrote:
> On 05 avril 22:43, Wolfgang Rohdewald wrote:
> > Hi,
>
> Hi,
>
> > I just thought I might not be the only one who would want something like
> that:
> >
> > If I have statements like
> >
> > # pylint: disable=W0613
> >
> > but pylint would n
On 05 avril 22:43, Wolfgang Rohdewald wrote:
> Hi,
Hi,
> I just thought I might not be the only one who would want something like that:
>
> If I have statements like
>
> # pylint: disable=W0613
>
> but pylint would not even warn without this statement,
> I would like to find those places.
>
