python-pylint-1.8.2-1.27

- Switch to regular releases again
- Update to 1.8.3:
  * Various false positives were fixed
  * Many additional python3 tweaks
  * For more see ChangeLog
- Drop test conditional as it is always on
- Add py2 and py3 bconds to allow building in the respective
  enviroments
- Run only python3 tests it takes ages to finish and we should focus
  only on one variant
  * Also few tests currently fail and upstream is aware so put there
    ||:
    https://github.com/PyCQA/pylint/issues/1847

- uninstall alternatives in %postun
- add update-alternatives requires

- update for singlespec
- enable test suite for all pythons
- update to 1.7.0 git pre-release, for python 3.6 support
  (boo#1026174)
  * multitude of new checkers
  * support for namespace packages
  * dropped pylint-gui
  * see changes in /usr/share/doc/packages/python-pylint/ChangeLog

- Update to version 1.6.5
  see changes in /usr/share/doc/packages/python-pylint/ChangeLog

- update source url

- Update to version 1.6.4
  see changes in /usr/share/doc/packages/python-pylint/ChangeLog

- Update to version 1.6.1
  see changes in /usr/share/doc/packages/python-pylint/ChangeLog

- Update to version 1.5.5:
  * Let visit_importfrom from Python 3 porting checker be called when everything is disabled
    Because the visit method was filtering the patterns it was expecting to be activated,
    it didn't run when everything but one pattern was disabled, leading to spurious false
    positives
  * Don't emit unsubscriptable-value for classes with unknown
    base classes.
  * Use an OrderedDict for storing the configuration elements
    This fixes an issue related to impredictible order of the disable / enable
    elements from a config file. In certain cases, the disable was coming before
    the enable which resulted in classes of errors to be enabled, even though the intention
    was to disable them. The best example for this was in the context of running multiple
    processes, each one of it having different enables / disables that affected the output.
  * Don't consider bare and broad except handlers as ignoring NameError,
    AttributeError and similar exceptions, in the context of checkers for
    these issues.

- Update to version 1.5.4
  * Merge StringMethodChecker with StringFormatChecker. This fixes a
    bug where disabling all the messages and enabling only a handful of
    messages from the StringFormatChecker would have resulted in no
    messages at all.
  * Don't apply unneeded-not over sets.

- Update to version 1.5.3:
  * Handle the import fallback idiom with regard to wrong-import-order.
    Closes issue #750.
  * Decouple the displaying of reports from the displaying of messages
    Some reporters are aggregating the messages instead of displaying
    them when they are available. The actual displaying was conflatted
    in the generate_reports. Unfortunately this behaviour was flaky
    and in the case of the JSON reporter, the messages weren't shown
    at all if a file had syntax errors or if it was missing.
    In order to fix this, the aggregated messages can now be
    displayed with Reporter.display_message, while the reports are
    displayed with display_reports.
    Closes issues #766 and #765.
  * Ignore function calls with variadic arguments without a context.
    Inferring variadic positional arguments and keyword arguments
    will result into empty Tuples and Dicts, which can lead in
    some cases to false positives with regard to no-value-for-parameter.
    In order to avoid this, until we'll have support for call context
    propagation, we're ignoring such cases if detected.
    Closes issue #722.
  * Treat AsyncFunctionDef just like FunctionDef nodes,
    by implementing visit_asyncfunctiondef in terms of
    visit_functiondef.
    Closes issue #767.
  * Take in account kwonlyargs when verifying that arguments
    are defined with the check_docs extension.
    Closes issue #745.
  * Suppress reporting 'unneeded-not' inside `__ne__` methods
    Closes issue #749.
- update to version 1.5.2:
  * Don't crash if graphviz is not installed, instead emit a warning
    letting the user to know.  Closes issue #168.
  * Accept only functions and methods for the deprecated-method
    checker.  This prevents a crash which can occur when an object
    doesn't have .qname() method after the inference.
  * Don't emit super-on-old-class on classes with unknown bases.
    Closes issue #721.
  * Allow statements in `if` or `try` blocks containing imports.
    Closes issue #714.
- update to version 1.5.1:
  * Fix a crash which occurred when old visit methods are encountered
    in plugin modules. Closes issue #711.
  * Add wrong-import-position to check_messages's decorator arguments
    for ImportChecker.leave_module This fixes an esoteric bug which
    occurs when ungrouped-imports and wrong-import-order are disabled
    and pylint is executed on multiple files.  What happens is that
    without wrong-import-position in check_messages, leave_module will
    never be called, which means that the first non-import node from
    other files might leak into the current file, leading to
    wrong-import-position being emitted by pylint.
  * Fix a crash which occurred when old visit methods are encountered
    in plugin modules. Closes issue #711.
  * Don't emit import-self and cyclic-import for relative imports of
    modules with the same name as the package itself.  Closes issues
    [#708] and #706.
- update to version 1.5.0:
  * long list of changes, see Changelog file for details
- Cleanup update-alternatives

- Remove execute bit from a test script to remove an unnecessary
  Requires. (bsc#1199219)