[pytest-dev] fixtures and pylint W0621

Brianna Laugher brianna.laugher at gmail.com
Mon Dec 9 04:22:51 CET 2013


Hi,

On 8 December 2013 20:40, holger krekel <holger at merlinux.eu> wrote:
>> My first reaction on this pylint issue was to see if this can not be
>> fixed wit a pylint plugin.  And I still think this would be nicer then
>> the other proposals of trying to figure out how to name fixtures
>> differently.  The way of declaring fixtures right now is very nice and
>> readable.  Especially if lahwran's suggestion is implemented as that
>> would make any mistakes obvious (and to an experience python developer
>> they already are obvious).
>
> Aiming for better pylint integration eg. through a plugin sounds like a
> great plan.  And one that does not require deep pytest knowledge -- so
> if someone here on the list is interested, i am willing to help design it.


I agree, I think a plugin is the way to go.

I have made a bit of an initial stab at a plugin:

https://bitbucket.org/pfctdayelise/pylint-pytest/

I am not sure the string building approach will get us very far, but I
just wanted to get something that would at least run (a lot of the
pylint docs are out of date).

Someone should probably run pylint over the pytest src to see what
other pylint messages are common.

cheers
Brianna

--
They've just been waiting in a mountain for the right moment:
http://modernthings.org/


More information about the Pytest-dev mailing list