I would like to get some feedback on these tools on:

- features;
- adaptability;
- ease of use and learning curve.



Pylint, PyChecker or PyFlakes?

I&#39;m trying to disable warning C0321 (&quot;more than one statement on a single line&quot; -- I often put `if` statements with short single-line results on the same line), in Pylint 0.21.1 (if it matters: astng 0.20.1, common 0.50.3, and Python 2.6.6 (r266:84292, Sep 15 2010, 16:22:56)).

I&#39;ve tried adding `disable=C0321` in the Pylint configuration file, but Pylint insists on reporting it anyway. Variations on that line (like `disable=0321` or `disable=C321`) are flagged as errors, so Pylint *does* recognize the option properly. It&#39;s just ignoring it.

Is this a Pylint bug, or am I doing something wrong? Is there a way around this?

I&#39;d really like to get rid of some of this noise.




How do I disable a Pylint warning?

I&#39;m running PyLint from inside Wing IDE on Windows. I have a sub-directory (package) in my project and inside the package I import a module from the top level, ie.

    __init__.py
    myapp.py
    one.py
    subdir\
        __init__.py
        two.py

Inside `two.py` I have `import one` and this works fine at runtime, because the top-level directory (from which `myapp.py` is run) is in the Python path. However, when I run PyLint on two.py it gives me an error:

    F0401: Unable to import &#39;one&#39;

How do I fix this?

PyLint &quot;Unable to import&quot; error - how to set PYTHONPATH?

For the following code:

    logger.debug(&#39;message: {}&#39;.format(&#39;test&#39;))

`pylint` produces the following warning:

&gt; **logging-format-interpolation (W1202):**
&gt; 
&gt; Use % formatting in logging functions and pass the % parameters as
&gt; arguments Used when a logging statement has a call form of
&gt; “logging.&lt;logging method&gt;(format_string.format(format_args...))”. Such
&gt; calls should use % formatting instead, but leave interpolation to the
&gt; logging function by passing the parameters as arguments.

I know I can turn off this warning, but I&#39;d like to understand it. I assumed using `format()` is the preferred way to print out statements in Python 3. Why is this not true for logger statements?

PyLint message: logging-format-interpolation

I have the following line in my header:

    import config.logging_settings

This actually changes my Python logging settings, but Pylint thinks it is an unused import. I do not want to remove `unused-import` warnings in general, so is it possible to just ignore this one specific line?

I wouldn&#39;t mind having a `.pylintrc` for this project, so answers changing a configuration file will be accepted.

Otherwise, something like this will also be appreciated:

    import config.logging_settings # pylint: disable-this-line-in-some-way





Is it possible to ignore one single specific line with Pylint?

Considering this code snippet:

    from os import walk

    files = []
    for (dirpath, _, filenames) in walk(mydir):
        # More code that modifies files
    if len(files) == 0: # &lt;-- C1801
        return None

I was alarmed by Pylint with this message regarding the line with the if statement:

&gt; [pylint] C1801:Do not use `len(SEQUENCE)` as condition value

The rule C1801, at first glance, did not sound very reasonable to me, and the [definition on the reference guide][1] does not explain why this is a problem. In fact, it downright calls it an _incorrect use_.

&gt; **len-as-condition (C1801)**:
&gt;      _Do not use `len(SEQUENCE)` as condition value Used when Pylint detects incorrect use of len(sequence) inside conditions._

My search attempts have also failed to provide me a deeper explanation. I do understand that a sequence&#39;s length property may be lazily evaluated, and that `__len__` can be programmed to have side effects, but it is questionable whether that alone is problematic enough for Pylint to call such a use incorrect. Hence, before I simply configure my project to ignore the rule, I would like to know whether I am missing something in my reasoning.

When is the use of `len(SEQ)` as a condition value problematic? What major situations is Pylint attempting to avoid with C1801?

  [1]: https://pylint.readthedocs.io/en/latest/reference_guide/features.html#id19




Why is the use of len(SEQUENCE) in condition values considered incorrect by Pylint?

I am using the following setup

- [macOS v10.14][1] (Mojave)
- Python 3.7.1
- Visual Studio Code 1.30
- Pylint 2.2.2
- Django 2.1.4

I want to use linting to make my life a bit easier in Visual Studio Code. However, for every import I have states &quot;unresolved import&quot;. Even on default Django imports (i.e. from django.db import models).

I presume it is because it is not seeing the virtual environment Python files.

Everything works just fine, but it&#39;s starting to get annoying.

The interpreter choices I have are all system versions of Python. It does not seem to see my virtual environment Python at all (it is not in the same directory as my workspace, so that part makes sense).

If I set up the *python.PythonPath* in the *settings.json* file, it just ignores it and does not list my virtual environment path as an option. I also tried setting it up in my global Python settings, but it also does not show up.

Is there a quick fix to get it working?

  [1]: https://en.wikipedia.org/wiki/MacOS_Mojave






Pylint &quot;unresolved import&quot; error in Visual Studio Code

I split up my class constructor by letting it call multiple functions, like this:

    class Wizard:
        def __init__(self, argv):
            self.parse_arguments(argv)
            self.wave_wand() # declaration omitted

        def parse_arguments(self, argv):
            if self.has_correct_argument_count(argv):
                self.name = argv[0]
                self.magic_ability = argv[1]
            else:
                raise InvalidArgumentsException() # declaration omitted

    # ... irrelevant functions omitted

While my interpreter happily runs my code, Pylint has a complaint:

`Instance attribute attribute_name defined outside __init__`

A cursory Google search is currently fruitless. Keeping all constructor logic in `__init__` seems unorganized, and turning off the Pylint warning also seems hack-ish.

What is a/the **Pythonic** way to resolve this problem?

Instance attribute attribute_name defined outside __init__

I am running Pylint on a Python project. Pylint makes many complaints about being unable to find NumPy members. How can I avoid this while avoiding skipping membership checks?

From the code:

    import numpy as np

    print np.zeros([1, 4])

Which, when ran, I get the expected:

&gt; [[ 0.  0.  0.  0.]]

However, Pylint gives me this error:

&gt; E:  3, 6: Module &#39;numpy&#39; has no &#39;zeros&#39; member (no-member)

For versions, I am using Pylint 1.0.0 (astroid 1.0.1, common 0.60.0) and trying to work with NumPy 1.8.0.


How do I get Pylint to recognize NumPy members?

I put a dict as the default value for an optional argument to a Python function, and pylint (using Sublime package) told me it was dangerous. Can someone explain why this is the case? And is a better alternative to use `None` instead?

Why is the empty dictionary a dangerous default value in Python?

I am running linux. Can I do something like `pylint --generate-rcfile &gt; .pylintrc` and then make changes to the resulting `.pylintrc` file to override the default settings? And if so should it be in my `~/` directory or should I put it in .pylint.d?

How do I create a pylintrc file

Pylint throws errors that some of the files are missing docstrings. I try and add docstrings to each class, method and function, but it seems that Pylint also checks that files should have a docstring at the beginning of them. Can I disable this somehow?

I would like to be notified of a docstring is missing inside a class, function or method, but it shouldn&#39;t be mandatory for a file to have a docstring.

(Is there a term for the legal jargon often found at the beginning of a proprietary source file? Any examples? I don&#39;t know whether it is a okay to post such a trivial question separately.)


How do I disable &quot;missing docstring&quot; warnings at a file-level in Pylint?

I would very much like to integrate [pylint][1] into the build process for
my python projects, but I have run into one show-stopper:  One of the
error types that I find extremely useful--:`E1101: *%s %r has no %r
member*`--constantly reports errors when using common django fields,
for example:

    E1101:125:get_user_tags: Class &#39;Tag&#39; has no &#39;objects&#39; member

which is caused by this code:

    def get_user_tags(username):
       &quot;&quot;&quot;
       Gets all the tags that username has used.
    
       Returns a query set.
       &quot;&quot;&quot;
       return Tag.objects.filter(  ## This line triggers the error.
           tagownership__users__username__exact=username).distinct()
    
    # Here is the Tag class, models.Model is provided by Django:
    class Tag(models.Model):
       &quot;&quot;&quot;
       Model for user-defined strings that help categorize Events on
       on a per-user basis.
       &quot;&quot;&quot;
       name = models.CharField(max_length=500, null=False, unique=True)
    
       def __unicode__(self):
           return self.name

How can I tune Pylint to properly take fields such as objects into account?  (I&#39;ve also looked into the Django source, and I have been unable to find the implementation of `objects`, so I suspect it is not &quot;just&quot; a class field.  On the other hand, I&#39;m fairly new to python, so I may very well have overlooked something.)


**Edit:** The only way I&#39;ve found to tell pylint to not warn about these warnings is by blocking all errors of the type (E1101) which is not an acceptable solution, since that is (in my opinion) an extremely useful error.  If there is another way, without augmenting the pylint source, please point me to specifics :)

See [here][2] for a summary of the problems I&#39;ve had with `pychecker` and `pyflakes` -- they&#39;ve proven to be far to unstable for general use.  (In pychecker&#39;s case, the crashes originated in the pychecker code -- not source it was loading/invoking.)

   [1]: http://www.logilab.org/857
   [2]: http://creswick.github.io/blog/2008/09/05/wrestling-python/

Using Pylint with Django

I&#39;m running Pylint on some code, and receiving the error &quot;Too few public methods (0/2)&quot;. What does this message mean?

The [Pylint documentation][1] is not helpful:

&gt; Used when a class has too few public methods, so be sure it&#39;s really worth it.

  [1]: http://docs.pylint.org/features.html#id22




What does Pylint&#39;s &quot;Too few public methods&quot; message mean?

I&#39;m still getting used to Python conventions and using Pylint to make my code more Pythonic, but I&#39;m puzzled by the fact that Pylint doesn&#39;t like single character variable names. I have a few loops like this:

    for x in x_values:
       my_list.append(x)

and when I run `pylint`, I&#39;m getting `Invalid name &quot;x&quot; for type variable (should match [a-z_][a-z0-9_]{2,30}` -- that suggests that a valid variable name must be between 3 and 31 characters long, but I&#39;ve looked through the [PEP8 naming conventions][1] and I don&#39;t see anything explicit regarding single lower case letters, and I do see a lot of examples that use them.

Is there something I&#39;m missing in PEP8 or is this a standard that is unique to Pylint?

  [1]: http://www.python.org/dev/peps/pep-0008/#naming-conventions



Why does Pylint object to single-character variable names?

I use Visual Studio Code to write Python code with Pylint.

When I press &lt;kbd&gt;Ctrl&lt;/kbd&gt; + &lt;kbd&gt;S&lt;/kbd&gt; (save), the editor wraps a long line into multiple short lines. How do I disable the action or configure wrap column count to 120 (default is 80)?

I have tried ` &quot;python.linting.pylintArgs&quot;: [&quot;--max-line-length=120&quot;]` and `&quot;editor.wordWrapColumn&quot;: 120`, but it didn&#39;t work.





Disable auto wrap long line in Visual Studio Code

We are using Pylint within our build system.

We have a Python package within our code base that has throwaway code, and I&#39;d like to disable all warnings for a module temporarily so I can stop bugging the other devs with these superfluous messages. Is there an easy way to `pylint: disable` all warnings for a module?




Disable all Pylint warnings for a file

I have 

    find . -iname &quot;*.py&quot; -exec pylint -E {} ;\

and

    FILES=$(find . -iname &quot;*.py&quot;)
    pylint -E $FILES

If I understand correctly, the first command will run pylint for each of the Python files, the second one will run pylint once for all files. I expected that both commands would return the same output, but they return different results. I think this diff is somehow related to imports and F (failure) pylint messages, which occurs when a import fails and is *not* output by pylint -E. 

Has someone already experienced this and could explain why the diff happens and what is the best way to run pylint?

Run Pylint for all Python files in a directory and all subdirectories

I am using prospector to examine my code. Pylint returned a `logging-not-lazy` warning about my debug message.

    Line: 31
      pylint: logging-not-lazy / Specify string format arguments as logging function parameters (col 16)   Line: 42
      pylint: logging-not-lazy / Specify string format arguments as logging function parameters (col 12)

My code is:

    logging.debug(&quot;detect mimetypes faild because %s&quot; % e )

How do I fix `logging-not-lazy` in pylint?

How to fix pylint logging-not-lazy?

I want to configure Pylint as an external tool in my entire project directory for a Python project that I&#39;m working on. I&#39;ve tried to use the repository as a module with ```__init__.py``` and without, and it&#39;s not working either way.

I&#39;m having difficulty setting up Pylint to run with PyCharm. I know that I should be running it as an external tool, however the settings confuse me.

The authoritative source on their documentation is broken, so I can&#39;t check that up either.



How to run Pylint with PyCharm

I want to run Python code in Microsoft Visual Studio Code but it gives an error:

&gt; Linter pylint is not installed

I installed:

* The Visual Studio Code Python extension
* Python&amp;nbsp;3
* Anaconda

How can I install Pylint?





Error message &quot;Linter pylint is not installed&quot;

Imagine a function which *dynamically* adds attributes to an object using `setattr`. The reason for doing so is that I want to map some external structure (e.g. a given parameter tree) to an object:

    my_object = SomeClass()
    apply_structure(my_object, some_descriptor)
    my_object.device1.enabled = True

Technically this works but of course Pylint rightly complains about &#39;device1&#39; being not a member of `SomeClass`.

I could disable the warning but that would be bad (because I still want to get the warning in all cases when the attribute does not exist because of misspelling, etc).

Is there a common and legal (Pylint-proof) way to dynamically add members to an object that not leads to warnings?

Alternatively: Can I disable Pylint for just one *object* rather than a line/block/file?

**Explanation**:

You might wonder why I should equip an object with member attributes dynamically when I plan to access these attributes in a hard-coded way later.

The reason is: I have a dynamic part of the program (where the decoration happens) and a static part which is *specialized* for a certain *scenario*. So I **could** also create a static class for this scenario but that would be overkill in a lot of situations. 

The following *specialized* code might allow access to some parameter of a device which might be attached to some bus:

    class MyDeviceHandler:
       on_get_some_subtree_element(self):
          return _some_internal_value
       on_set_some_subtree_element(self, value):
          _some_internal_value = value

    dev = MyDeviceHandler()
    
    decorate_object_with_device_structure(dev, &#39;some/attached/device&#39;)

    dev.some.subtree.element = 5       &lt;--- will call the set-callback
    x = dev.some.subtree.element       &lt;--- will call the get-callback

So the structure behind `&#39;some/attached/device&#39;` might be arbitrary and very complex and I don&#39;t want to reproduce it in a class structure.

One way to get rid of this warning would be to create/access a `dict` based tree:

    dev[&#39;some&#39;][&#39;subtree&#39;][&#39;element&#39;] = 5

But this is harder to write and not nice to read - I would only do this to quieten Pylint.


Avoid Pylint warning E1101: &#39;Instance of .. has no .. member&#39; for class with dynamic attributes

I have a module-level variable in my Python 2.6 program named &quot;_log&quot;, which PyLint complains about:

    C0103: Invalid name &quot;_log&quot; (should match (([A-Z_][A-Z0-9_]*)|(__.*__))$)

Having read [this answer][1] I understand why it&#39;s doing this: it thinks the variable is a constant and applies the constant regex. However, I beg to differ: I think it&#39;s a variable. How do I tell PyLint that, so it doesn&#39;t complain? How does PyLint determine whether it&#39;s a variable or a constant - does it just treat all module-level variables as constants?


  [1]: https://stackoverflow.com/questions/709490/python-code-convention-using-pylint/709709#709709

How do I tell PyLint &quot;it&#39;s a variable, not a constant&quot; to stop message C0103?

I&#39;m receiving a Pylint error regarding my constant: `MIN_SOIL_PARTICLE_DENS` (invalid name).
Any ideas why this constant is wrong? Here&#39;s my full function:



    def bulk_density(clay, sand, organic_matter):
        MIN_SOIL_PARTICLE_DENS = 2.65
        x1 = (0.078 + 0.278 * sand + 0.034 * clay + 0.022 * organic_matter - 0.018
              * sand * organic_matter - 0.027 * clay * organic_matter - 0.584 * sand
              * clay)
        x2 = -0.107 + 1.636 * x1
        field_capacity = vol_water_content_33_j_kg(clay, sand, organic_matter)#m3/m3
        sat_water_content = 0.043 + field_capacity + x2 - 0.097 * sand
        return (1 - sat_water_content) * MIN_SOIL_PARTICLE_DENS



Pylint invalid constant name

I&#39;ve seen [How can you find unused functions in Python code?][1] but that&#39;s really old, and doesn&#39;t really answer my question. 

I have a large python project with multiple libraries that are shared by multiple entry point scripts. This project has been accreting for many years with many authors, so there&#39;s a whole lot of dead code. You know the drill. 

I  know that finding all dead code is un-decidable. All I need is a tool that will find all functions that are not called anywhere. We&#39;re not doing anything fancy with calling functions based on the string of the function name, so I&#39;m not worried about anything pathological... 

I just installed pylint, but it appears to be file based, and not paying much attention to interfile dependencies, or even function dependencies.

Clearly, I could grep for def in all of the files, get all of the function names from that, and do a grep for each of those function names. I&#39;m just hoping that there&#39;s something a little smarter than that out there already.

ETA: Please note that I don&#39;t expect or want something perfect. I know my halting-problem-proof just as well anyone (No really I taught theory of computation I know when I&#39;m looking at something that is recursively enumerable). Any thing that tries to approximate it by actually running the code is going to take way too long. I just want something that syntactically goes through the code and says &quot;This function is definitely used. This function MIGHT be used, and this function is definitely NOT used, no one else even seems to know it exists!&quot; And the first two categories aren&#39;t important. 

  [1]: https://stackoverflow.com/questions/693070/how-can-you-find-unused-functions-in-python-code

Finding dead code in large python project

I have a pylint message (w0707) on this piece of code (from https://www.django-rest-framework.org/tutorial/3-class-based-views/):

```
class SnippetDetail(APIView):
    &quot;&quot;&quot;
    Retrieve, update or delete a snippet instance.
    &quot;&quot;&quot;
    def get_object(self, pk):
        try:
            return Snippet.objects.get(pk=pk)
        except Snippet.DoesNotExist:
            raise Http404
```

the message is:  
`Consider explicitly re-raising using the &#39;from&#39; keyword`  
I don&#39;t quite understand how to act to correct the problem.  
Thank you in advance for your help


Pylint raise-missing-from

I have a line like this:

    filter(lambda x: x == 1, [1, 1, 2])

Pylint is showing a warning:

    W:  3: Used builtin function &#39;filter&#39;

Why is that? is a list comprehension the recommended method?

Of course I can rewrite this like this:

    [x for x in [1, 1, 2] if x == 1]

And I get no warnings, but I was wondering if there&#39;s a PEP for this?

Why doesn&#39;t Pylint like built-in functions?

I want to refactor a big Python function into smaller ones. For example, consider this following code snippet:

    x = x1 + x2 + x3 + x4 + x5 + x6 + x7 + x8 + x9

Of course, this is a trivial example. In practice, the code is more complex. My point is that it contains many local-scope variables that would have to be passed to the extracted function, which could look like:

    def mysum(x1, x2, x3, x4, x5, x6, x7, x8, x9):
        x = x1 + x2 + x3 + x4 + x5 + x6 + x7 + x8 + x9
        return x

The problem is that Pylint would trigger a warning about too many arguments.

I could avoid the warning by doing something like:

    def mysum(d):
        x1 = d[&#39;x1&#39;]
        x2 = d[&#39;x2&#39;]
        ...
        x9 = d[&#39;x9&#39;]
        x = x1 + x2 + x3 + x4 + x5 + x6 + x7 + x8 + x9
        return x

    def mybigfunction():
        ...
        d = {}
        d[&#39;x1&#39;] = x1
        ...
        d[&#39;x9&#39;] = x9
        x = mysum(d)

but this approach loos ugly to me. It requires writing a lot of code that is even redundant.

Is there a better way to do it?





Python: avoiding Pylint warnings about too many arguments

I have a Python function that takes a list as a parameter. If I set the parameter&#39;s default value to an empty list like this:

    def func(items=[]):
        print items

Pylint would tell me &quot;Dangerous default value [] as argument&quot;. So I was wondering what is the best practice here?


Best practice for setting the default value of a parameter that&#39;s supposed to be a list in Python?

I have just tried to lint some code with Pylint, and the last remaining error is

    R0902: too-many-instance-attributes (8/7)

I understand the rationale behind limiting the number of instance attributes, but seven seems a bit low. I also realise that the linter should not have the last word. However, I would like to know what I should be doing instead of:

    def __init__(self, output_file=None, output_dir=None):
        &quot;&quot;&quot;
        Set the frobnicator up, along with default geometries
        &quot;&quot;&quot;

        self.margin = 30

        self.pos = [0, 0]
        self.sep = [5, 5]

        self.cell = [20, 20]

        self.frobbr = library.Frobbr()

        page = self.frobbr.get_settings(&#39;page&#39;)

        self.lim = [page.get_width() - self.margin,
                    page.get_height() - self.margin]

        self.filename = output_file
        self.moddir = output_dir

Should I package the geometries up into a dict, do something else to stop Pylint complaining, or just ignore it (which I don&#39;t really want to do)?

How to deal with Pylint&#39;s &quot;too-many-instance-attributes&quot; message?

I&#39;m learning pytest and I lint my code with pylint.
But pylint still complaints about:  
`W0621: Redefining name %r from outer scope (line %s)`

for the following example from pytest:

    # test_wallet.py
    
    @pytest.fixture
    def my_wallet():
        &#39;&#39;&#39;Returns a Wallet instance with a zero balance&#39;&#39;&#39;
        return Wallet()
    
    @pytest.mark.parametrize(&quot;earned,spent,expected&quot;, [
        (30, 10, 20),
        (20, 2, 18),
    ])
    def test_transactions(my_wallet, earned, spent, expected):
        my_wallet.add_cash(earned)
        my_wallet.spend_cash(spent)
        assert my_wallet.balance == expected

Redefining name `my_wallet` from outer scope.

I found workaround to add `_` prefix to the fixture name: `_my_wallet`.

What would be the best practice if I want to keep fixtures in same file as functions?  

 1. Prepend all fixtures with `_`?
 2. Disable this `pylint` check for tests?
 3. Better suggestion?

pytest fixtures Redefining name from outer scope [pylint]

I am learning to program with python and I am having issues with importing from a module in a package. I am usingvisual studio code with Python 3.8.2 64 bit. 

[My Project Directory][1]

    .vscode
    ├── ecommerce
    │&#160;&#160; ├── __init__.py
    │   ├── database.py
    │&#160;&#160; ├── products.py
    │&#160;&#160; └── payments
    │       ├── __init__.py
    │&#160;&#160;     ├── authorizenet.py
    │&#160;&#160;     └── paypal.py
    ├── __init__.py
    └── main.py

  [1]: https://i.stack.imgur.com/ZQZhP.png

in the `ecommerce/products.py` file I have:

```python
#products.py
from .database import Database
p = Database(3,2)
```

So that I can import the `Database` class from the `ecommerce/database.py` file. But I get error

    ImportError : Attempted relative import with no known parent package

ImportError : Attempted relative import with no known parent package

I have a python class and ran pylint against it. One message it gave was:

    Warning: Method could be a function

Is this telling me that it would be better to move this method out of the class because it doesn&#39;t use any instance variables? 

In C# I would make this a static method. What&#39;s the most pythonic thing to do here? 

How to handle the pylint message: Warning: Method could be a function

I am running pylint on an opencv project and I am getting many pylint errors in VS code about  members not being present.

Example code:

    import cv2
    cv2.imshow(....)

Errors obtained: 

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/4Kbdh.png

However , the code runs correctly without any errors.

Versions : pylint 1.8.1 , astroid 1.6.0

PyLint not recognizing cv2 members

I&#39;m using PyQt and am running into this issue.  If my import statements are:

    from PyQt4.QtCore import *
    from PyQt4.QtGui import *

then pylint gives hundreds of &quot;Unused import&quot; warnings.  I&#39;m hesitant to just turn them off, because there might be other unused imports that are actually useful to see.  Another option would be to do this:

    from PyQt4.QtCore import Qt, QPointF, QRectF
    from PyQt4.QtGui import QGraphicsItem, QGraphicsScene, ...

and I end up having 9 classes on the QtGui line.  There&#39;s a third option, which is:

    from PyQt4 import QtCore, QtGui

and then prefix all the classes with QtCore or QtGui whenever I use them.

At this point I&#39;m agnostic as to which one I end up doing in my project, although the last one seems the most painful from my perspective.  What are the common practices here?  Are there technical reason to use one style over the other?

Should wildcard import be avoided?

I have a Flask (v0.10.1) application using Flask-SQLAlchemy (v2.0) and I&#39;m trying to configure Pylint to check it. Running with Python 3.4.2.

First error was:

     Instance of &#39;SQLAlchemy&#39; has no &#39;Table&#39; member (no-member)

And I fixed this one ignoring the check for member attributes on SQLAlchemy:

    ignored-classes=SQLAlchemy

But I&#39;m having a problem with the query member on entities:

    Class &#39;UserToken&#39; has no &#39;query&#39; member (no-member)

Is there any way to fix this issue without having to ignore no-member errors on every query call?

---

Flask bootstrap:

    from flask import Flask
    from flask_sqlalchemy import SQLAlchemy

    db = SQLAlchemy()
    app = Flask(__name__)
    db.init_app(app)
    app.run()

UserToken entity:

    from app import db
    
    class UserToken(db.Model):
        user_token_id = db.Column(db.Integer, primary_key=True, index=True)
        token_auth = db.Column(db.String(64), unique=True, nullable=False, index=True)

The controller:

    from entities import UserToken

    token = UserToken.query.filter(
        UserToken.token_auth == token_hash,
    ).first()

Pylint can&#39;t find SQLAlchemy query member

I made a simple python script to post data on a website.

    #Imports
    
    url_to_short = sys.argv[1]
    
    post_url = &#39;https://www.googleapis.com/urlshortener/v1/url&#39;
    headers = {&#39;Content-Type&#39;: &#39;application/json&#39;}
    
    data = {&#39;longUrl&#39;: url_to_short}
    post_data = json.dumps(data)
    
    req = urllib2.Request(post_url, post_data, headers)
    resp = urllib2.urlopen(req)
    
    if resp.getcode() == 200:  
        content = json.loads(resp.read())
    
    #Other stuff

Now I thought lets check my script for coding standards with `pylint` tool.

My `pylint` output is as follows:


    ************* Module post
    C:  1,0: Missing docstring
    C:  6,0: Invalid name &quot;url_to_short&quot; (should match (([A-Z_][A-Z0-9_]*)|(__.*__))$)
    C:  8,0: Invalid name &quot;post_url&quot; (should match (([A-Z_][A-Z0-9_]*)|(__.*__))$)
    C:  9,0: Invalid name &quot;headers&quot; (should match (([A-Z_][A-Z0-9_]*)|(__.*__))$)
  
    # Other stuff


Now, my question is why `pylint` is showing my variable names as `Invalid name`. Is naming variable this way a wrong coding convention.

My [complete pylint output][1].


  [1]: http://pastie.org/3994703

Pylint showing invalid variable name in output

The following is from the [Pylint documentation][1]:

```lang-none
--ignore=&lt;file&gt;
    Add &lt;file or directory&gt; to the black list. It should be a 
    base name, not a path. You may set this option multiple 
    times. [current: %default]
```

Yet, I&#39;m not having luck getting the directory part work.

I have directory called *migrations*, which has django-south migration files. As I enter --ignore=migrations, it still keeps giving me the errors/warnings in files inside the *migrations* directory.

Could it be that `--ignore` is not working for directories?

If I could even use a regular expression to match the ignored files, it would work, since django-south files are all named 0001_something, 0002_something...

----

Since I could not get the ignore by directory to work, I have resorted to simply putting `# pylint: disable-msg-cat=WCREFI` on top of each migration file, which ignores all Pylint errors, warnings, and information.

  [1]: http://linux.die.net/man/1/pylint





Ignore by directory using Pylint

In Python, if some methods of a class need a helper function, but the helper function itself doesn&#39;t use anything in the class, should I put the helper function inside or outside the class?

I tried putting it inside but PyLint was complaining that this function could have been put outside.

@Karl:

The class is a software upgrader and the helper function creates a new folder if the folder doesn&#39;t exist yet. The class is in a module having pretty much only the code for the class as of now. Other classes may be added later on.

Python - Should I put my helper functions inside or outside the class?

We&#39;ve been long-time fans of `pylint`. Its static analysis has become a critical part of all our python projects and has saved tons of time chasing obscure bugs.  But after upgrading from 1.3 -&gt; 1.4, almost all compiled c extensions result in E1101(no-member) errors.  

Projects that previously run perfectly clean through `pylint` 1.3 now complain about almost every C extension member with E1101. We&#39;ve been forced to disable E1101 errors, but this materially detracts from the usefulness of `pylint`.

For example, this perfectly valid use of the `lxml` package

    r&quot;&quot;&quot;valid.py: demonstrate pylint 1.4 error&quot;&quot;&quot;
    from lxml import etree
    print etree.Element(&#39;mydoc&#39;)

Run this through `pylint`, and it reports:

    $ pylint -rn valid.py
    No config file found, using default configuration
    ************* Module valid
    E:  3, 6: Module &#39;lxml.etree&#39; has no &#39;Element&#39; member (no-member)

But it is perfectly valid:

    $ python valid.py
    &lt;Element mydoc at 7fddf67b1ba8&gt;

Here&#39;s where it gets really weird. A very small handful of C extensions seem to work just fine through `pylint`, e.g.:

    r&quot;&quot;&quot;valid2.py: this one works fine&quot;&quot;&quot;
    import sqlite3
    print sqlite3.version

    $ pylint -rn valid2.py
    No config file found, using default configuration
 
My question is, has anyone else witnessed this? And if so, would you be willing to share your workaround/solution?

We&#39;ve experimented with trying to create plugins to suppress these warnings
(http://docs.pylint.org/plugins.html#enter-plugin), but we&#39;re having difficulty making heads or tails of the docs -- and the `astroid` base class is uber-complex and has defied our attempts to grok it.

For real bonus points (and our eternal gratitude) we&#39;d love to understand what changed in `pylint`.  We&#39;d be happy to fix the code (or at least publish a best practice document for C extension authors) that would satisfy `pylint`. 

Platform details

    $ pylint --version
    No config file found, using default configuration
    pylint 1.4.0,
    astroid 1.3.2, common 0.63.2
    Python 2.7.5 (default, Jul  1 2013, 18:09:11)
    [GCC 4.4.7 20120313 (Red Hat 4.4.7-3)]



All Pylint Solutions on Gang of Coders

Total of 40 Pylint Solutions