On Sat, Apr 18, 2020 at 08:38:21PM +0200, Christoph Zwerschke wrote: > Am 18.04.2020 um 20:18 schrieb Justin Pryzby: > > It works fine when I use import _pg, which is what I started doing at > > telsasoft before raising this issue, and what I'll plan to continue. > The explanation is probably the same, because pylint doesn't analyze C > extensions by default, so it ignores any imports from there. That's why your > import statement is ignored and why it does not know that pg has these > attributes because they were imported from the C extension. > > > The pep8 style portion of flake8 is so naggy as to be useless to me. > > Note that you can ignore and modify various checks that you find too > restrictive in pylint and flake8 using their configuation files, adapting > them a bit more to your personaly/company style.
I use pylint -E but since we still have -E errors to clean up, I can't bother with anything else, and it finds a wide variety of the most interesting issues. I just did a round of cleanup with flake8, but it's limited to unused variables and imports. 16 files changed, 6 insertions(+), 34 deletions(-) I used flake8 --ignore=E,W, ignoring all pep8 warnings and pep8 errors, leaving very little from pyflakes, half of which are some kind of false positive. -- Justin _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo/pygresql
