Changelog for python2-pylint-1.9.2-16.21.noarch.rpm :

* Thu Dec 06 2018 Tomáš Chvátal - Fix fdupes call
* Wed Sep 19 2018 Tomáš Chvátal - Provide also python-pylint namespace
* Wed Sep 19 2018 Tomáš Chvátal - Fix out testsuite to work on python2
* Tue Sep 18 2018 Tomáš Chvátal - Split out the python2 variant as the new releases are py3 only
* Mon Jul 16 2018 tchvatalAATTsuse.com- Enable tests and make sure they pass
* Sun Jul 15 2018 michaelAATTstroeder.com- Update to 1.9.2:
* New Python 3 checkers
* Added two new Python 3 porting checks
* Added a new deprecated-sys-function check
* Added xreadlines-attribute check
* Wed Jan 24 2018 tchvatalAATTsuse.com- Switch to regular releases again- Update to 1.8.2:
* 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
* Wed Mar 29 2017 jmatejekAATTsuse.com- uninstall alternatives in %postun- add update-alternatives requires
* Wed Mar 01 2017 jmatejekAATTsuse.com- 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
* Wed Feb 01 2017 michaelAATTstroeder.com- Update to version 1.6.5 see changes in /usr/share/doc/packages/python-pylint/ChangeLog
* Wed Jan 11 2017 ecsosAATTopensuse.org- update source url
* Mon Aug 15 2016 michaelAATTstroeder.com- Update to version 1.6.4 see changes in /usr/share/doc/packages/python-pylint/ChangeLog
* Thu Jul 07 2016 michaelAATTstroeder.com- Update to version 1.6.1 see changes in /usr/share/doc/packages/python-pylint/ChangeLog
* Sat May 07 2016 michaelAATTstroeder.com- 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.
* Fri Feb 12 2016 jweberhoferAATTweberhofer.at- 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.
* Wed Jan 13 2016 toddrme2178AATTgmail.com- 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
* Wed Sep 02 2015 mciharAATTsuse.cz- Update to 1.4.4:
* Avoid breaking pylint when using logilab.common >= 1.0.
* Mon Mar 16 2015 mciharAATTsuse.cz- Update to 1.4.3:
* Remove three warnings: star-args, abstract-class-little-used, abstract-class-not-used. These warnings don\'t add any real value and they don\'t imply errors or problems in the code.
* Added a new option for controlling the peephole optimizer in astroid. The option ``--optimize-ast`` will control the peephole optimizer, which is used to optimize a couple of AST subtrees. The current problem solved by the peephole optimizer is when multiple joined strings, with the addition operator, are encountered. If the numbers of such strings is high enough, Pylint will then fail with a maximum recursion depth exceeded error, due to its visitor architecture. The peephole just transforms such calls, if it can, into the final resulting string and this exhibit a problem, because the visit_binop method stops being called (in the optimized AST it will be a Const node).
* Thu Mar 12 2015 mciharAATTsuse.cz- Update to 1.4.2:
* Don\'t require a docstring for empty modules. Closes issue #261.
* Fix a false positive with `too-few-format-args` string warning, emitted when the string format contained a normal positional argument (\'{0}\'), mixed with a positional argument which did an attribute access (\'{0.__class__}\'). Closes issue #463.
* Take in account all the methods from the ancestors when checking for too-few-public-methods. Closes issue #471.
* Catch enchant errors and emit \'invalid-characters-in-docstring\' when checking for spelling errors. Closes issue #469.
* Use all the inferred statements for the super-init-not-called check. Closes issue #389.
* Add a new warning, \'unichr-builtin\', emitted by the Python 3 porting checker, when the unichr builtin is found. Closes issue #472.
* Add a new warning, \'intern-builtin\', emitted by the Python 3 porting checker, when the intern builtin is found. Closes issue #473.
* Add support for editable installations.
* The HTML output accepts the `--msg-template` option. Patch by Dan Goldsmith.
* Add \'map-builtin-not-iterating\' (replacing \'implicit-map-evaluation\'), \'zip-builtin-not-iterating\', \'range-builtin-not-iterating\', and \'filter-builtin-not-iterating\' which are emitted by `--py3k` when the appropriate built-in is not used in an iterating context (semantics taken from 2to3).
* Add a new warning, \'unidiomatic-typecheck\', emitted when an explicit typecheck uses type() instead of isinstance(). For example, `type(x) == Y` instead of `isinstance(x, Y)`. Patch by Chris Rebert. Closes issue #299.
* Add support for combining the Python 3 checker mode with the --jobs flag (--py3k and --jobs). Closes issue #467.
* Add a new warning for the Python 3 porting checker, \'using-cmp-argument\', emitted when the `cmp` argument for the `list.sort` or `sorted builtin` is encountered.
* Make the --py3k flag commutative with the -E flag. Also, this patch fixes the leaks of error messages from the Python 3 checker when the errors mode was activated. Closes issue #437.
* Wed Feb 18 2015 mciharAATTsuse.cz- Update to 1.4.1:
* Look only in the current function\'s scope for bad-super-call. Closes issue #403.
* Check the return of properties when checking for not-callable. Closes issue #406.
* Warn about using the input() or round() built-ins for Python 3. Closes issue #411.
* Proper abstract method lookup while checking for abstract-class-instantiated. Closes issue #401.
* Use a mro traversal for finding abstract methods. Closes issue #415.
* Fix a false positive with catching-non-exception and tuples of exceptions.
* Fix a false negative with raising-non-exception, when the raise used an uninferrable exception context.
* Fix a false positive on Python 2 for raising-bad-type, when raising tuples in the form \'raise (ZeroDivisionError, None)\'.
* Fix a false positive with invalid-slots-objects, where the slot entry was an unicode string on Python 2. Closes issue #421.
* Add a new warning, \'redundant-unittest-assert\', emitted when using unittest\'s methods assertTrue and assertFalse with constant value as argument. Patch by Vlad Temian.
* Add a new JSON reporter, usable through -f flag.
* Add the method names for the \'signature-differs\' and \'argument-differs\' warnings. Closes issue #433.
* Don\'t compile test files when installing.
* Fix a crash which occurred when using multiple jobs and the files given as argument didn\'t exist at all.
* Mon Dec 08 2014 mciharAATTsuse.cz- Lower tk dependency to Recommends as it\'s only needed for optional GUI
* Mon Dec 08 2014 mciharAATTsuse.cz- Update to 1.4.0:
* Added new options for controlling the loading of C extensions. By default, only C extensions from the stdlib will be loaded into the active Python interpreter for inspection, because they can run arbitrary code on import. The option `--extension-pkg-whitelist` can be used to specify modules or packages that are safe to load.
* Change default max-line-length to 100 rather than 80
* Drop BaseRawChecker class which were only there for backward compat for a while now
* Don\'t try to analyze string formatting with objects coming from function arguments. Closes issue #373.
* Port source code to be Python 2/3 compatible. This drops the need for 2to3, but does drop support for Python 2.5.
* Each message now comes with a confidence level attached, and can be filtered base on this level. This allows to filter out all messages that were emitted even though an inference failure happened during checking.
* Improved presenting unused-import message. Closes issue #293.
* Add new checker for finding spelling errors. New messages: wrong-spelling-in-comment, wrong-spelling-in-docstring. New options: spelling-dict, spelling-ignore-words.
* Add new \'-j\' option for running checks in sub-processes.
* Added new checks for line endings if they are mixed (LF vs CRLF) or if they are not as expected. New messages: mixed-line-endings, unexpected-line-ending-format. New option: expected-line-ending-format.
* \'dangerous-default-value\' no longer evaluates the value of the arguments, which could result in long error messages or sensitive data being leaked. Closes issue #282
* Fix a false positive with string formatting checker, when encountering a string which uses only position-based arguments. Closes issue #285.
* Fix a false positive with string formatting checker, when using keyword argument packing. Closes issue #288.
* Proper handle class level scope for lambdas.
* Handle \'too-few-format-args\' or \'too-many-format-args\' for format strings with both named and positional fields. Closes issue #286.- Switched to tar.gz upstream
* Tue Nov 04 2014 mciharAATTsuse.cz- Update to 1.3.1:
* Fix a false positive with string formatting checker, when encountering a string which uses only position-based arguments. Closes issue #285.
* Fix a false positive with string formatting checker, when using keyword argument packing. Closes issue #288.
* Handle \'too-few-format-args\' or \'too-many-format-args\' for format strings with both named and positional fields. Closes issue #286.
* Analyze only strings by the string format checker. Closes issue #287.
* Properly handle nested format string fields. Closes issue #294.
* Properly handle unicode format strings for Python 2. Closes issue #296.
* Fix a false positive with \'too-few-format-args\', when the format strings contains duplicate manual position arguments. Closes issue #310.
* fixme regex handles comments without spaces after the hash. Closes issue #311.
* Fix a crash encountered when looking for attribute docstrings.
* Fix a crash which ocurred while checking for \'method-hidden\', when the parent frame was something different than a function.