Skip to content

Conversation

@PCManticore
Copy link
Contributor

Hi,

A small Pylint related issue.

We're trying to move away from using numeric message ids for errors and warnings, since they can not be easily remembered, slowly becoming a second class citizen. Instead, Pylint uses symbolic names, which don't carry as much information as the numerical ids (from what checker they're coming for instance), but they can be remembered easily and carry a semantic meaning due to their natural language expressiveness.

Also, this patch removes the mentions to wikidot, since it's not sanctioned by Pylint as an official source of documentation, its use being an artifact from Pylint's past.

Pylint tries to move away from using numeric message ids
for its errors and warnings, since they can not be easily remembered,
slowly becoming a second class citizen. Instead, Pylint uses symbolic names,
which don't carry as much information as the numerical ids, but they can
be remembered easily and carry a semantic meaning due to their natural
language expresiveness.
Also, this patch removes the mentions to wikidot, since it's not sanctioned
by pylint as an official source of documentation, its use being an artifact
from pylint's past.
@programmdesign
Copy link
Contributor

Hi, thanks for your commit. Do we really have to remove the links? I know the messages change, but referencing the message descriptions would be nice.

@PCManticore
Copy link
Contributor Author

We could leave them as is for now, even though they aren't officially sanctioned by Pylint. On the other hand, I could link up pylint's documentation instead, but unfortunately it's not so user friendly and I can't give a link to individual message descriptions. What do you think we should do?

@programmdesign
Copy link
Contributor

Let's just stick to your commit ;-)

programmdesign added a commit that referenced this pull request Sep 22, 2015
Mention Pylint's symbolic names along with message ids
@programmdesign programmdesign merged commit d2c6d69 into quantifiedcode:master Sep 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants