trigger a deprecationwarning for Result.excinfo about pluggy HOT 7 CLOSED

@RonnyPfannschmidt works for me.

from pluggy.

@RonnyPfannschmidt wait so we don't want to allow for public access at all?
Is the idea that users can catch the underlying exception instead from get_result()?

from pluggy.

correct

from pluggy.

@RonnyPfannschmidt waiting on you still as per your #155 comment as to how to move forward with an alternative system for this.

from pluggy.

@tgoodlet thanks for the reminder, i still haven't come up with a reasonable failure indication system, i believe this will require a little collaborative brainstorming to generate ideas

from pluggy.

What was the rationale for not exposing the exception object again?

from pluggy.

closing this one as it will disappear with the deprecation/removal of result objects in #260

from pluggy.