Mailman 3 June 2018 - code-quality

pylint-unittest plugin to detect less than optimal usage of assertions in your unittest usage
by Federico Bond July 16, 2018

July 16, 2018

Hello, I wrote a Pylint plugin to detect less than optimal usage of unittest assertions, for example writing self.assertEqual(x, None) instead of self.assertIsNone(x) or using deprecated aliases. It's published in PyPI under the name pylint-unittest and is also available on GitHub here: https://github.com/federicobond/pylint-unittest I would love to hear your feedback on it. Also, it took me longer than I expected to put together the necessary boilerplate for doing test-driven development on this plugin, so I hope it can serve as a good base for others too. I feel that the way pylint-django tests are structured is too awkward for newcomers. Thank you! Federico

2 2

Need help: pylintrc breaks black_list from plugins
by Alexander Todorov June 29, 2018

June 29, 2018

Hi folks, according to this bug report: https://github.com/PyCQA/pylint-django/issues/167#issuecomment-401304800 when there is a .pylintrc file with an ignore line inside of it it this overrides the black_list options configured by plugins. In the case of pylint_django we would like to ignore some directories (like migrations) and this breaks. In pylint_django we have: def register(linter): linter.config.black_list += ('migrations', 'south_migrations') and from what I can tell after this is set something calls OptionsProviderMixIn.set_option and overrides it afterwards. Is that a desired behavior or a bug? If this is a bug where should I look if I want to contribute a patch ? Regards, Alex

1 0

Making a new release of flake8 happen
by Jimi Cullen June 27, 2018

June 27, 2018

Dear all, There's a lot of people itching for a new version of flake8, especially since the current version on PyPI is incompatible with the latest versions of pyflakes and pycodestyle. Flake8 still works with the versions of those packages as specified in the requirements of flake8 - but in practice people are updating those packages regardless and running into problems with flake8. Plus it would just be nice to have an update and be able to use the new features and bux fixes of those packages. I submitted a fix for compatibility with pycodestyle a while ago, which has been merged into the flake8 master branch. There are a couple of pull requests open on gitlab to get it to work with pyflakes too. What can I/we do to make a new release happen? I understand the maintainer (Ian) is extremely busy, and the community has been quite aggressively demanding of him. I am very sympathetic to his situation. Maybe the project needs additional active maintainers? I would volunteer, but I'm not qualified as: - I'm very inexperienced with open source stuff (I've only had two PRs accepted - in pycodestyle and flake8 - both with support and encouragement from Ian). - I've never put a python package together or put anything on PyPI etc. - Basically I use python every day at work, but as a financial data analyst, not building and packaging systems for others to use. Does anyone have any suggestions for how to proceed? Best wishes, Jimi Cullen

2 1

Problems in pylint.1
by esr＠thyrsus.com June 12, 2018

June 12, 2018

This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database. See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification date of any manual page. You may wish to do that by hand. I apologize if this message seems spammy or impersonal. The volume of markup bugs I am tracking is over five hundred - there is no real alternative to generating bugmail from a database and template. -- Eric S. Raymond Problems with pylint.1: Ambiguous or invalid backslash. This doesn't cause groff a problem. but it confuses doclifter and may confuse older troff implementations. --- pylint.1-unpatched 2018-05-18 08:21:03.576466143 -0400 +++ pylint.1 2018-05-18 08:21:03.392467392 -0400 @@ -231,7 +231,7 @@ .IP "--max-line-length=<int>" Maximum number of characters on a single line. [current: 100] .IP "--ignore-long-lines=<regexp>" -Regexp for a line that is allowed to be longer than the limit. [current: ^\s*(# )?<?https?://\S+>?$] +Regexp for a line that is allowed to be longer than the limit. [current: ^\es*(# )?<?https?://\eS+>?$] .IP "--single-line-if-stmt=<y_or_n>" Allow the body of an if to be on the same line as the test if there is no else. [current: no] .IP "--no-space-check=NO_SPACE_CHECK"

1 0