deprecated string module issue

[Stephen Hansen]

On Fri, Jun 25, 2010 at 7:02 AM, GrayShark <howe.steven at gmail.com> wrote:

> Thanks for the suggestion. I gave it a quick try. Same 'warning'. No,
> using the string module is the issue. Perhaps I'll just ignore it.
>

Perhaps? Why perhaps? The warning is simply factually wrong-- therefore,
there's no reason in the world not to ignore it. You can submit a bug to the
pylint people though, that may be nice :)

Remember that pylint is a third-party tool made by a group of people who
have a certain understanding and set of expectations for what's good / bad /
right / wrong.  It isn't *really* an authoritative voice of "what is
supported by Python" or "what is good Python code" -- and they even know
that, which is why exactly what warnings and such it spits out are *very*
configurable, so it can be adjusted to different peoples needs and
standards.

Its a very useful metric, but consider what it spits out advice and not
necessarily errors or problems that need addressing. You have to decide that
for yourself on a case-by-case basis.

--S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20100625/80ffab63/attachment-0001.html>