Ticket #2049 (closed defect: fixed)
Broken parsing in pylint
| Reported by: | dwyerk | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.8.5 |
| Version: | 0.8.4p1 | Keywords: | |
| Cc: |
Description
The change shown here https://github.com/buildbot/buildbot/commit/d013e2ce85aaf8a8e5378edb716f72abf3cef76b breaks pylint when using the option include-ids=yes in your pylintrc. What you really want is to make those d{4}'s optional.
Change History
comment:2 Changed 23 months ago by dustin
- Priority changed from major to minor
- Milestone changed from undecided to 0.8.5
comment:3 Changed 23 months ago by dwyerk
include-ids=yes, output-format=parseable
test.py:1: [C0103, whatABadFunctionName] Invalid name "whatABadFunctionName" (should match [a-z_][a-z0-9_]{2,30}$)
include-ids=no, output-format=parseable
test.py:1: [C, whatABadFunctionName] Invalid name "whatABadFunctionName" (should match [a-z_][a-z0-9_]{2,30}$)
include-ids=yes, output-format=text
C0103: 1:whatABadFunctionName: Invalid name "whatABadFunctionName" (should match [a-z_][a-z0-9_]{2,30}$)
include-ids=no, output-format=text
C: 1:whatABadFunctionName: Invalid name "whatABadFunctionName" (should match [a-z_][a-z0-9_]{2,30}$)
Note: See
TracTickets for help on using
tickets.
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
Can you give some example strings so that we can test this?