code-quality July 2016

code-quality@python.org

10 participants
8 discussions

Importing __version__ / __author__ without causing an unused import error
by Jack Wilsdon 27 Jul '16

27 Jul '16

Hi, I'm looking for a way to import __version__ / __author__ into my __init__.py without causing an F401 error. Defining __version__ normally works fine: > init.py __version__ = '1.0.0' __author__ = 'Jack Wilsdon <jack.wilsdon(a)gmail.com> But if I define them in an external file and import them, I get an F401 error: > __version__.py __version__ = '1.0.0' __author__ = 'Jack Wilsdon <jack.wilsdon(a)gmail.com> > init.py from __version__ import __version__, __author__ # I get an F > flake8 __init__.py __init__.py:1:1: F401 '__version.__author__' imported but unused __init__.py:1:1: F401 '__version.__version__' imported but unused Is there anything I can do about this? I know I could add "# noqa: F401" to the end of the import, but it just feels like a bit of a "hack" to me. I could also add __version__ and __author__ to __all__ in init.py, but then they would be imported if anyone used "from my_module import *", which is definitely not what I want. Is this a bug in flake8/pyflakes or just my understanding of how __version__ and __author__ are exempt from F401 errors normally. Thanks, Jack

3 2

Announcing ci.pycqa.org
by Ian Cordasco 25 Jul '16

25 Jul '16

Hey all! So, Rackspace has provided us with some sponsorship so we can run things like Jenkins! This allows us to run ci.pycqa.org. Flake8 has been using this for continuous integration with GitLab for a while now, but we've recently moved the public address from ci.sigmavir.us (my temporary domain) to ci.pycqa.org and added more build capacity. We should also have money enough to add more build nodes if necessary. We currently support python 2.6, 2.7, 3.3, 3.4, 3.5, and pypy's latest 5.x branch for Python environments. The controlling Jenkins node (that you see at ci.pycqa.org) is running Ubuntu 14.04 while the solitary build node is running 16.04. We also support GitHub Pull Requests and we can probably support other linux variants as well. Presently I'm the sole administrator of all of this, but I'd still like to make sure the larger group can take advantage of it. As for future facing plans, I'd kind of like to utilize Jenkins to its fullest potential, including building wheels after successful builds for PRs for Flake8. This will make it easier for me to install and test the PR itself. I don't presently have that set-up *yet* and I haven't quite figured out how I would do that, but if that sounds interesting to you, let's chat (on this mailing list or in private). Finally, I just wanted to thank Rackspace again (and Jesse Noller in particular) for this sponsorship. If you're one of those inclined to tweet, you should thank Jesse @jessenoller. I'm sure he'd appreciate it. Cheers, Ian

2 3

Module checking
by mrx 22 Jul '16

22 Jul '16

Hi, Thanks a lot for a wonderful and very useful tool in pylint. I am interested in having pylint check that the 'interface' specified in the __init__.py is respected and no one is importing stuff outside that interface. Is there something like this available in pylint? If not, could you give me some hints how to write it? I don't have a lot of experience with the pylint codebase though. Thanks in advance! Patrik

1 0

[pylint] disabled messages with --errors-only
by Tim Stumbaugh 20 Jul '16

20 Jul '16

Hi, Since command line flags are processed after config file directives, error messages that are disabled in a config file (or in a command line flag that appears before --errors-only) are not respected when running in errors-only mode. This appears to be because errors-only mode unconditionally enables all messages with a category of 'E' or 'F'. We have a config file that has the messages that has a few error messages disabled (because of highly-dynamic features that we use that pylint can't interpret correctly), but we do run pylint in errors-only mode quite often. A patch that works for us is to change PyLinter.disable_noerror_messages not to ever enable messages (but only to disable non error messages). That seems like quite a large change though, since a user who only passes --enable (or enables messages through the config file) would not get messages in --errors-only that they haven't asked for. Is there an opinion on what patch might be acceptable for the project? Would it work to add an extra flag or put extra state in the PyLinter object so that it knows which messages have been explicitly disabled? Thanks, tjs -- Tim Stumbaugh Operations Hudson River Trading

2 2

Need pointers on how to add test case in the test suite for the functionality I am adding.
by Ahirnish Pareek 11 Jul '16

11 Jul '16

Hi Devs, I am kind of confused as to how to write test case for my functionality. I am adding the patch in typecheck.py. Is there any guide on adding new test cases? Thanks. -- Regards, Ahirnish

2 1

Pylint 1.6.0 released
by Claudiu Popa 07 Jul '16

07 Jul '16

Hi folks, I am joyful to announce the release of Pylint 1.6.0. This is the next minor release in the 1.X branch and most probably the last one, since we are preparing the taking off of Pylint 2.0. This release has a couple of small improvements, bug fixes and new checks, comparing to the last one. You can find more about was changed in this release here: https://docs.pylint.org/en/1.6.0/whatsnew/1.6.html https://docs.pylint.org/en/1.6.0/whatsnew/changelog.html#what-s-new-in-pyli… As usual, don't hesitate to report any new bugs you might encounter with this release. We are also looking for new contributors, so if you feel like taking a stab at a bug or a feature you would like in pylint, open up an issue and let's talk! We are also planning to do releases more often from now on and you can see what we are planning for the next releases here: https://github.com/PyCQA/pylint/milestones Thank you and enjoy, Claudiu Popa

1 0

class diagram dot code of pylint/pyreverse as stdout stream output
by Florian Kromer 07 Jul '16

07 Jul '16

Hi everyone, is it possible to pipe the dot code of a pylint/pyreverse package or class diagram into the stdout stream instead of creating a .dot file and putting it in there? A bit more details: I write a sphinx-doc extension which shall integrate the dot representation of package and class diagrams generated with pylint/pyreverse into sphinx-doc documentations on the fly. It would be easier for me to integrate the dot code of pylint/pyreverse from its stdout stream instead of struggling with files to get the dot code... Thanks. Florian

2 2

PyCQA News
by Ian Cordasco 07 Jul '16

07 Jul '16

Hey all, It's been a while since we talked about new things happening in the PyCQA. We have new projects and a couple other tiny announcements. New projects! ============= We've added pyflakes and flake8-import-order to our tiny group of folks and of course we're still open to other projects. There is discussion on the Jedi issue tracker (https://github.com/davidhalter/jedi/issues/630) about moving a project that can provide a unified AST to various projects (including some PyCQA projects) into the organization as well. OpenHUB Organization! ===================== We now have an organization on OpenHub: https://www.openhub.net/orgs/PyCQA This means that projects and developers can show their affiliation with the organization. Doing so is *not* mandatory but I thought it might be fun for some people, plus we're part of a fairly small group of people testing this feature for OpenHUB. pycqa.org ========= A little while back I registered the domain and started using sub-domains for documentation, e.g., pydocstyle.pycqa.org flake8.pycqa.org etc. If you have a project in the PyCQA and would like one of those sub-domains for your docs, let me know. They're *very* easy to set-up with ReadTheDocs. New Logo! ========= You might have noticed on our OpenHUB organization or on our GitLab and GitHub organizations, but if you didn't we have a Logo! Glynnis Ritchie made our logo for us and collaborated with the rest of us over on https://github.com/PyCQA/meta/issues/1 Gitter.im ========= We already have (and some of us use) ##python-code-quality on Freenode's IRC servers. IRC, however, is still rather unpopular so some members have started discussing a better persistent chat option (https://github.com/PyCQA/meta/issues/11) and have started testing Gitter.im. Blog (Coming soon) ================== We started discussing a new blog for the organization as a whole: https://github.com/PyCQA/meta/issues/14 I think we can just use Sphinx + ReadTheDocs and a domain hack for all of this. If you have other ideas, weigh in on the issue. Cheers, Ian (sigmavirus24)

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

code-quality July 2016