On 01/05/2013 01:49 PM, Jan Riechers wrote:
On 05.01.2013 03:11, someone wrote:
But about the regular expressions (a bit deeper look into that):
Like said of Chris:
[a-z]
defines a "catching group", in this case all ascii lowercase letters
ranging from "a" to "z". If noting else is provided, the
On 05.01.2013 03:11, someone wrote:
On 01/03/2013 12:27 PM, Chris Angelico wrote:
On Thu, Jan 3, 2013 at 10:19 PM, someone wrote:
Doesn't this "[ ... ]" mean something optional?
What does {2,30}$ mean?
I think $ means that the {2,30} is something in the end of the
sentence...
You can find
On 01/03/2013 03:56 AM, Dave Angel wrote:
The first lint program I recall hearing of was available in the early
1980's, and was for the C language. At the time, the C language was
extremely flexible (in other words, lots of ways to shoot yourself in
the foot) and the compiler was mostly of the p
On 01/03/2013 12:39 PM, Peter Otten wrote:
someone wrote:
On 01/03/2013 10:00 AM, Peter Otten wrote:
Terry Reedy wrote:
[a-z_][a-z0-9_]{2,30}$) - so I suppose it wants this name to end with
[an
underscore ?
No, it allows underscores. As I read that re, 'rx', etc, do match. They
No, it's
On 01/03/2013 12:27 PM, Chris Angelico wrote:
On Thu, Jan 3, 2013 at 10:19 PM, someone wrote:
Doesn't this "[ ... ]" mean something optional?
What does {2,30}$ mean?
I think $ means that the {2,30} is something in the end of the sentence...
You can find regular expression primers all over t
On 01/03/2013 05:52 PM, Terry Reedy wrote:
That seems like a improper error message from the tool. "Invalid name"
does *not* properly describe that situation. The name is *not*
"Invalid" in any sense of the word, and a "checker" that tells you it is
is creating needless false-positives. An er
On 1/3/2013 9:19 AM, Mike C. Fletcher wrote:
On 13-01-02 09:48 PM, Terry Reedy wrote:
...
2) self.lightDone: Invalid name "lightDone" (should match
[a-z_][a-z0-9_]{2,30}$)
So I can now understand that pylint doesn't like my naming convention
with a capital letter in the middle of the variable
On 13-01-02 09:48 PM, Terry Reedy wrote:
...
2) self.lightDone: Invalid name "lightDone" (should match
[a-z_][a-z0-9_]{2,30}$)
So I can now understand that pylint doesn't like my naming convention
with a capital letter in the middle of the variable name, like:
"lightDone" = a boolean value. I s
someone wrote:
> On 01/03/2013 10:00 AM, Peter Otten wrote:
>> Terry Reedy wrote:
>>
[a-z_][a-z0-9_]{2,30}$) - so I suppose it wants this name to end with
[an
underscore ?
>>>
>>> No, it allows underscores. As I read that re, 'rx', etc, do match. They
>>
>> No, it's one leading lett
On Thu, Jan 3, 2013 at 10:19 PM, someone wrote:
> Doesn't this "[ ... ]" mean something optional?
>
> What does {2,30}$ mean?
>
> I think $ means that the {2,30} is something in the end of the sentence...
You can find regular expression primers all over the internet, but to
answer these specific
On 01/03/2013 10:00 AM, Peter Otten wrote:
Terry Reedy wrote:
[a-z_][a-z0-9_]{2,30}$) - so I suppose it wants this name to end with an
underscore ?
No, it allows underscores. As I read that re, 'rx', etc, do match. They
No, it's one leading letter or underscore [a-z_] plus at least two lett
On 01/03/2013 03:55 AM, Ian Kelly wrote:
On Wed, Jan 2, 2013 at 7:24 PM, someone wrote:
3) self.rx / rself.ry / self.rz: Invalid name "rx" (should match
[a-z_][a-z0-9_]{2,30}$) - so I suppose it wants this name to end with an
underscore ?
It wants the name to be at least 3 characters long.
Terry Reedy wrote:
>> [a-z_][a-z0-9_]{2,30}$) - so I suppose it wants this name to end with an
>> underscore ?
>
> No, it allows underscores. As I read that re, 'rx', etc, do match. They
No, it's one leading letter or underscore [a-z_] plus at least two letters,
underscores or digits [a-z0-9_]{
On Wed, Jan 2, 2013 at 10:01 PM, Ben Finney wrote:
> Ian Kelly writes:
>
>> On Wed, Jan 2, 2013 at 7:24 PM, someone wrote:
>> > 1) class somethingWork: Invalid name "somethingWork" (should match
>> > [A-Z_][a-zA-Z0-9]+$), I'm not that good at regular exps, but I
>> > suppose it wants my class na
Ian Kelly writes:
> On Wed, Jan 2, 2013 at 7:24 PM, someone wrote:
> > 1) class somethingWork: Invalid name "somethingWork" (should match
> > [A-Z_][a-zA-Z0-9]+$), I'm not that good at regular exps, but I
> > suppose it wants my class name to start with a capital letter ?
>
> Yes, PEP-8 recommen
On 01/02/2013 09:31 PM, someone wrote:
> On 01/02/2013 08:31 PM, Ian Kelly wrote:
>> On Wed, Jan 2, 2013 at 10:57 AM, Chris Angelico
>> wrote:
>>> Yeah, same applies to most linters I think. You end up disagreeing
>>> with the author on half the points. Oh well. Doesn't make the tool
>>> useless,
On Wed, Jan 2, 2013 at 7:24 PM, someone wrote:
> 1) class somethingWork: Invalid name "somethingWork" (should match
> [A-Z_][a-zA-Z0-9]+$), I'm not that good at regular exps, but I suppose it
> wants my class name to start with a capital letter ?
Yes, PEP-8 recommends CamelCase for class names.
On 1/2/2013 9:24 PM, someone wrote:
What pylint says is:
1) class somethingWork: Invalid name "somethingWork" (should match
[A-Z_][a-zA-Z0-9]+$), I'm not that good at regular exps, but I suppose
it wants my class name to start with a capital letter ?
Yes
2) self.lightDone: Invalid name "lig
On 01/02/2013 08:31 PM, Ian Kelly wrote:
On Wed, Jan 2, 2013 at 10:57 AM, Chris Angelico wrote:
Yeah, same applies to most linters I think. You end up disagreeing
with the author on half the points. Oh well. Doesn't make the tool
useless, just means you need to fiddle with it to get it how you
On 01/03/2013 12:52 AM, Steven D'Aprano wrote:
On Wed, 02 Jan 2013 09:26:32 -0500, Dave Angel wrote:
Global const values should be ALL_CAPS, so it's obvious that nobody
intends to modify them.
Like math.pi I suppose? *wink*
:-)
It's the non-const global attributes that expect to be under
On 01/02/2013 03:26 PM, Dave Angel wrote:
On 01/02/2013 09:09 AM, someone wrote:
On 01/02/2013 01:07 PM, Peter Otten wrote:
OMG... I don't want to type those underscores everywhere... Anyway,
thank you very much for explaining the meaning of what it wants...
Global const values should be AL
On Wed, Jan 2, 2013 at 4:52 PM, Steven D'Aprano
wrote:
> If pylint says that global variables should be named like "__variable__",
> that is explicitly going against PEP 8.
It doesn't say that anywhere. It includes dunder names in the regex
so that you don't get spurious warnings from pylint abo
On Wed, 02 Jan 2013 09:26:32 -0500, Dave Angel wrote:
> On 01/02/2013 09:09 AM, someone wrote:
>> On 01/02/2013 01:07 PM, Peter Otten wrote:
>>> pylint wants global names to be uppercase (what PEP 8 recommends for
>>> constants) or "special" (two leading and two trailing underscores):
>>>
>>> THA
On Wed, Jan 2, 2013 at 10:57 AM, Chris Angelico wrote:
> Yeah, same applies to most linters I think. You end up disagreeing
> with the author on half the points. Oh well. Doesn't make the tool
> useless, just means you need to fiddle with it to get it how you want
> it.
It's a lot less work to di
On Thu, Jan 3, 2013 at 4:52 AM, Ian Kelly wrote:
> On Wed, Jan 2, 2013 at 7:32 AM, Chris Angelico wrote:
>> Okay, I have to ask... why? Does it have an exception for names of classes?
>
> Yes, and for module-level functions.
Oh, okay. So the check's a lot more specific than the message implies
-
On Wed, Jan 2, 2013 at 7:32 AM, Chris Angelico wrote:
> Okay, I have to ask... why? Does it have an exception for names of classes?
Yes, and for module-level functions.
> I don't like linters that enforce too much style. Catch things that
> might be mis-coded (like C's classic "if (x = 1)"), but
On Wed, Jan 2, 2013 at 11:07 PM, Peter Otten <__pete...@web.de> wrote:
> someone wrote:
>> Another thing is that I don't understand this warning:
>>
>> Invalid name "original_format" (should match (([A-Z_][A-Z0-9_]*)|
>> > (__.*__))$)
>>
>> I get it everywhere... I don't understand how it wants me
On 01/02/2013 09:09 AM, someone wrote:
> On 01/02/2013 01:07 PM, Peter Otten wrote:
>> someone wrote:
>>
>>> On 01/01/2013 01:56 PM, Peter Otten wrote:
>>
from module import * # pylint: disable=W0622
>>>
>>> Oh, I just learned something new now... How come I cannot type
>>> "#pylint:
>>> enabl
On 01/02/2013 01:07 PM, Peter Otten wrote:
someone wrote:
On 01/01/2013 01:56 PM, Peter Otten wrote:
from module import * # pylint: disable=W0622
Oh, I just learned something new now... How come I cannot type "#pylint:
enable=W0622" in the line just below the import ?
With what intended
someone wrote:
> On 01/01/2013 01:56 PM, Peter Otten wrote:
>> from module import * # pylint: disable=W0622
>
> Oh, I just learned something new now... How come I cannot type "#pylint:
> enable=W0622" in the line just below the import ?
With what intended effect?
> Another thing is that I don'
30 matches
Mail list logo
