Lars Hupfeldt Nielsen

Hi Ned, thank you for your quick response. Yes, I deliberately run all test against the installed package. This is the only way to make 'sure' that the package will...

Any chance of this making it into 2.0 (or 1.3.x)?

Sad. This seems like a needed feature in order to generate proper detailed reports.

Well, actually I care about the feature, not the PR itself :)

No, the wrong behaviour only occurs when `pylint-pytest`is involved. The coverage files are deleted before I get a chance to combine them. Without `pylint-pytest` it works as expected. @nedbat wrote...

I ran into the same problem. Storing the path relative to CWD (I got '.') is not of much use. Storing the path as both relative to project **and** as...

> Is the finish message really needed, or just a "by the way"? The finish messages were "by the way" :)

And I agree that an exception should not be hidden, so a `post` message should not be a replacement for the exception message/stacktrace. The nice thing about declared post message...

#640 is merged, is anything else blocking a new release? This is preventing us from testing with the same versions that we use in our Jenkins deployments.

A colleague of mine just reported a plugin compatibility issue. I told him to wait for this. Is there anything we can do to assist?