Re: [code-quality] Europython 14

Hi, we'll have a PyLint sprint in room C04 at EuroPython starting Wednesday, so if you just want to meet up with us, drop by in that room. Maybe we could also have a BoF session about static Python analysis? // Torsten On Thu, Jul 17, 2014 at 5:15 PM, Sylvain Thénault < sylvain.thena...@logilab

[code-quality] Static Analysis Dinner on Friday @ EuroPython

Hi all, we thought it'd be nice to go and have a dinner together with people interested in static analysis. My suggestion is to go to Pri Maria ( http://www.primaria.de/). Let's meet tomorrow at 6:30pm, at the bcc entrance. Getting to the restaurant will take about 30min. If you want to come, pl

[code-quality] [ANN] Astroid 1.3 released

Hello! I'm happy to announce the availability of astroid 1.3. Functional changes in this release are mostly bugfixes and small improvements, the large change is that support for Python versions < 2.7 has been dropped, which allows us to support Python 2.7 and 3.3+ from a single codebase, without

Re: [code-quality] How to detect unused PyLint declarations

Yes, I0021 is useless-suppression. There's also suppressed-message, to show what kinds of messages have been suppressed. Looking at that every once in a while is interesting as well. Especially for badly understood messages, there is a tendency in developers to just paper over the warnings instead

Re: [code-quality] Advice regarding caching values as a side-effect of visiting classes

Hi Anne, you can write a checker that simply stores all classes it encounters and then walks the inheritance tree to find all violations in `close`. This checker method is called after all modules specified on the commandline have been checked, but before reports are generated, so emitting warning

Re: [code-quality] Lots of E1101 in standard modules after upgrading pylint to 1.4.0

Hi, this might be a bug in astroid, I'll have a look at it later this week. // Torsten 2014-11-26 15:41 GMT+01:00 Paul Smith : > On Wed, 2014-11-26 at 02:03 -0500, Paul Smith wrote: > > Forgot to say, I'm running on GNU/Linux Ubuntu GNOME 14.10 and I've > built all these tools (including python

Re: [code-quality] Lots of E1101 in standard modules after upgrading pylint to 1.4.0

('time') Thanks! // Torsten 2014-11-26 22:00 GMT+01:00 Torsten Marek : > Hi, > > this might be a bug in astroid, I'll have a look at it later this week. > > // Torsten > > 2014-11-26 15:41 GMT+01:00 Paul Smith : > >> On Wed, 2014-11-26 at 02:03 -05

Re: [code-quality] Lots of E1101 in standard modules after upgrading pylint to 1.4.0

Yeah, that looks like the problem. Let me play around with this a little bit, there are some subtleties with virtualenvs. We'll have an official fix soon. // Torsten 2014-11-26 23:27 GMT+01:00 Paul Smith : > On Wed, 2014-11-26 at 17:14 -0500, Paul Smith wrote: > > if os.name == 'nt': > >

Re: [code-quality] Lots of E1101 in standard modules after upgrading pylint to 1.4.0

Fixed at head. Until there's a new release, you can also use the hidden pylint option --unsafe-load-any-extension=y // Torsten 2014-11-27 19:35 GMT+01:00 Torsten Marek : > Yeah, that looks like the problem. Let me play around with this a little > bit, there are some subtleties with

Re: [code-quality] Time cost for pylint analyses?

Hi Anne, should be fairly simple, yes. What kind of breakdown do you mean, by module/package or by checker? // Torsten 2014-12-04 22:41 GMT+01:00 Anne Mulhern : > Hi! > > Would it be possible to be able to extend pylint somehow to > record a time cost for individual pylint analyses? > > - mulhe