Hello!
On behalf of the Pylint development team, I'm happy to announce that Pylint 1.4 has been released.
This release has a lot of improvements over the last one. One of the main differences is that support for Python versions < 2.7 has been droped, which allows us to support Python 2.7 and 3.3+ from a single codebase.
Other important changes:
* A Python 3 porting checker, activated by the new flag '--py3k'. This mode will disable all other checkers and will emit warnings and errors for constructs which are invalid or removed in Python 3.
* 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.
* An experimental support for using multiple workers to process files and packages, activated with the new --jobs flag.
* A new spelling checker (disabled by default).
* New warnings: boolean-datetime, logging-format-interpolation, inherit-non-class, mixed-line-endings
* A lot of other small improvements and bug fixes.
If you find any bugs, don't hesitate to open a new issue on our issue tracker.
Enjoy!
On 11/23/14 4:45 AM, Claudiu Popa wrote:
Hello!
On behalf of the Pylint development team, I'm happy to announce that Pylint 1.4 has been released.
This release has a lot of improvements over the last one. One of the main differences is that support for Python versions < 2.7 has been droped, which allows us to support Python 2.7 and 3.3+ from a single codebase.
Other important changes:
BTW: it would be great to include a link to the full list of changes, wherever they might be.
- A new spelling checker (disabled by default).
If you find any bugs, don't hesitate to open a new issue on our issue tracker.
I found a problem with the new spell feature, but the issue tracker (http://www.bytebucket.org/logilab/pylint/issues) seems broken: everything I tried ended at a 403 CSRF validation failure page.
Is there another way to report problems?
On Thu, Nov 27, 2014 at 5:19 PM, Ned Batchelder ned@nedbatchelder.com wrote:
On 11/23/14 4:45 AM, Claudiu Popa wrote:
Hello!
On behalf of the Pylint development team, I'm happy to announce that Pylint 1.4 has been released.
This release has a lot of improvements over the last one. One of the main differences is that support for Python versions < 2.7 has been droped, which allows us to support Python 2.7 and 3.3+ from a single codebase.
Other important changes:
BTW: it would be great to include a link to the full list of changes, wherever they might be.
Indeed. We don't have right now a full list of changes, except the changelog for 1.4: https://bitbucket.org/logilab/pylint/src/ede9e9ebc2557f768e129f29aeb365608ae...
- A new spelling checker (disabled by default).
If you find any bugs, don't hesitate to open a new issue on our issue tracker.
I found a problem with the new spell feature, but the issue tracker (http://www.bytebucket.org/logilab/pylint/issues) seems broken: everything I tried ended at a 403 CSRF validation failure page.
Is there another way to report problems?
Hm, isn't it bitbucket.org? Never encountered bytebucket.org until now.
On Thu, Nov 27, 2014 at 10:19:28 -0500, Ned Batchelder wrote:
I found a problem with the new spell feature, but the issue tracker (http://www.bytebucket.org/logilab/pylint/issues) seems broken: everything I tried ended at a 403 CSRF validation failure page.
Not sure where that url came from, afaik the tracker is https://bitbucket.org/logilab/pylint/issues
Cheers, Julien
-
Claudiu Popa -
Julien Cristau -
Ned Batchelder